Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a059f4ac06821eb1704395e48d0bf5a106d7e04bbb112a9710c664174cf02b3f

Tx prefix hash: 06c6683616b100205368521e5d02c12066f59a2373ff8c45a6bcc6033582f6da
Tx public key: b28cc9d552add7d7b2259e4fe55517f3dc71b09809c94efbc0b3deb61b412aba
Timestamp: 1728011157 Timestamp [UCT]: 2024-10-04 03:05:57 Age [y:d:h:m:s]: 00:190:17:56:00
Block: 1123976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136120 RingCT/type: yes/0
Extra: 01b28cc9d552add7d7b2259e4fe55517f3dc71b09809c94efbc0b3deb61b412aba02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3b74638362bb63a2e0a1d895cc3b1304ac4492f7d07c94a4f1e2dc5d229805b 0.600000000000 1606527 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1123986, "vin": [ { "gen": { "height": 1123976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3b74638362bb63a2e0a1d895cc3b1304ac4492f7d07c94a4f1e2dc5d229805b" } } ], "extra": [ 1, 178, 140, 201, 213, 82, 173, 215, 215, 178, 37, 158, 79, 229, 85, 23, 243, 220, 113, 176, 152, 9, 201, 78, 251, 192, 179, 222, 182, 27, 65, 42, 186, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8