Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7356cbc36435185e4c39671fec3c3d1534248d640ea765a1e9cd36270bd7177

Tx prefix hash: 3b4560169dd9e6a66b0c4e63f780ac15496f9c443db173dfb5324f60dcff8bea
Tx public key: 33b2bbc3ae6f1427bac6c7ea6f522f626854087b9fc8df01f795805036008fe0
Timestamp: 1710545518 Timestamp [UCT]: 2024-03-15 23:31:58 Age [y:d:h:m:s]: 00:344:21:20:58
Block: 979185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246564 RingCT/type: yes/0
Extra: 0133b2bbc3ae6f1427bac6c7ea6f522f626854087b9fc8df01f795805036008fe00211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d58ff742512838b2e1e4e69b81ef1e15efee238ecf69b3f2e91b521734920113 0.600000000000 1439218 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": 979195, "vin": [ { "gen": { "height": 979185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d58ff742512838b2e1e4e69b81ef1e15efee238ecf69b3f2e91b521734920113" } } ], "extra": [ 1, 51, 178, 187, 195, 174, 111, 20, 39, 186, 198, 199, 234, 111, 82, 47, 98, 104, 84, 8, 123, 159, 200, 223, 1, 247, 149, 128, 80, 54, 0, 143, 224, 2, 17, 0, 0, 0, 7, 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