Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f0fbda837edde464a0ed6d28a2ca7e0418bc679975a79de9e4d756a0e6a504c

Tx prefix hash: f05347ac999f14c4daf2a7dbf30b941d5e519ab01b06804af955ee20d79bd842
Tx public key: 4992baa9d7765fab85b9066ca3c289ce5df0bb16b11aaba834f7ca8ee69ea858
Timestamp: 1740143617 Timestamp [UCT]: 2025-02-21 13:13:37 Age [y:d:h:m:s]: 00:229:09:29:37
Block: 1224079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161669 RingCT/type: yes/0
Extra: 014992baa9d7765fab85b9066ca3c289ce5df0bb16b11aaba834f7ca8ee69ea8580211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cb39aeaf1eab77f39357e3a0a5c3d21d6057aaf689e25f629b0aa528ce65d2f 0.600000000000 1710936 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": 1224089, "vin": [ { "gen": { "height": 1224079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cb39aeaf1eab77f39357e3a0a5c3d21d6057aaf689e25f629b0aa528ce65d2f" } } ], "extra": [ 1, 73, 146, 186, 169, 215, 118, 95, 171, 133, 185, 6, 108, 163, 194, 137, 206, 93, 240, 187, 22, 177, 26, 171, 168, 52, 247, 202, 142, 230, 158, 168, 88, 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