Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc591253613dfbc0cb3ce1ef90192385a9ab4721df9a316eb1962639fe131eae

Tx prefix hash: 4aa5badc75c8f0c63f0aedf1e57c7c4f645af975d7d93ef2d921ca6562efee2c
Tx public key: 6da1015096096d7e03acad1fd20fdb1ba6ad2b9a7eab80fa0403ce494adba0ae
Timestamp: 1739202523 Timestamp [UCT]: 2025-02-10 15:48:43 Age [y:d:h:m:s]: 00:355:20:12:41
Block: 1216313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251996 RingCT/type: yes/0
Extra: 016da1015096096d7e03acad1fd20fdb1ba6ad2b9a7eab80fa0403ce494adba0ae0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 777814b85933d8d7b623f10044d14f80480ec9d3317c199759923fd8f4e35f8c 0.600000000000 1703118 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": 1216323, "vin": [ { "gen": { "height": 1216313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "777814b85933d8d7b623f10044d14f80480ec9d3317c199759923fd8f4e35f8c" } } ], "extra": [ 1, 109, 161, 1, 80, 150, 9, 109, 126, 3, 172, 173, 31, 210, 15, 219, 27, 166, 173, 43, 154, 126, 171, 128, 250, 4, 3, 206, 73, 74, 219, 160, 174, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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