Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab0ba40c847048093533a85a7c2d17f8c53b4b0c25779c38dbbce7087ee71c36

Tx prefix hash: 7c1fd76a72c2268fbe8a31ca8404b455b2db951ded33b410460ae398c23d7478
Tx public key: cc95baaf211e464997881d05a6d75ba18c6782dc2cba49693214e8d38f6959fd
Timestamp: 1704101938 Timestamp [UCT]: 2024-01-01 09:38:58 Age [y:d:h:m:s]: 01:313:07:36:39
Block: 925746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482763 RingCT/type: yes/0
Extra: 01cc95baaf211e464997881d05a6d75ba18c6782dc2cba49693214e8d38f6959fd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab71a69ca3be15aad8eaed8db1521b23cda384bc6cbcbb45dc032c28a7de22e2 0.600000000000 1383512 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": 925756, "vin": [ { "gen": { "height": 925746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab71a69ca3be15aad8eaed8db1521b23cda384bc6cbcbb45dc032c28a7de22e2" } } ], "extra": [ 1, 204, 149, 186, 175, 33, 30, 70, 73, 151, 136, 29, 5, 166, 215, 91, 161, 140, 103, 130, 220, 44, 186, 73, 105, 50, 20, 232, 211, 143, 105, 89, 253, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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