Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a9a9482005867b743bafd35185c368ca114585a9a564a4c57ffbbde6891b217

Tx prefix hash: 92455a3eff68d952a1f5184825c77d8b37eb0628f02118a07ef2c4d1d92296ad
Tx public key: cdd19ba0a6160fd13dd6c1dc553c63f41f496def57330de557e6cd3b647f341c
Timestamp: 1737301350 Timestamp [UCT]: 2025-01-19 15:42:30 Age [y:d:h:m:s]: 00:154:09:13:52
Block: 1200807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109999 RingCT/type: yes/0
Extra: 01cdd19ba0a6160fd13dd6c1dc553c63f41f496def57330de557e6cd3b647f341c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 827e04f9429a3cbfac1d4e417b374b84763e6e4e94c7424ec0736f4e45a6e696 0.600000000000 1687454 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": 1200817, "vin": [ { "gen": { "height": 1200807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "827e04f9429a3cbfac1d4e417b374b84763e6e4e94c7424ec0736f4e45a6e696" } } ], "extra": [ 1, 205, 209, 155, 160, 166, 22, 15, 209, 61, 214, 193, 220, 85, 60, 99, 244, 31, 73, 109, 239, 87, 51, 13, 229, 87, 230, 205, 59, 100, 127, 52, 28, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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