Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b350cd8d6950d942223d37cdf83896ff45b94c54898a94e8d265ed4ed15650b

Tx prefix hash: 596c110f83379270336f6c2655d504cb3141308532a5444722462aef96c91118
Tx public key: 8c1065ca0f5a2ca3ea8869062c3bb79d3f6d9f4928e71cc4f930d3499dc26311
Timestamp: 1715632991 Timestamp [UCT]: 2024-05-13 20:43:11 Age [y:d:h:m:s]: 00:330:20:02:57
Block: 1021347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236478 RingCT/type: yes/0
Extra: 018c1065ca0f5a2ca3ea8869062c3bb79d3f6d9f4928e71cc4f930d3499dc263110211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b882379352533b8d63a3be6146e2d90909fc754a703bdc2bd383b8b07168b4f 0.600000000000 1485644 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": 1021357, "vin": [ { "gen": { "height": 1021347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b882379352533b8d63a3be6146e2d90909fc754a703bdc2bd383b8b07168b4f" } } ], "extra": [ 1, 140, 16, 101, 202, 15, 90, 44, 163, 234, 136, 105, 6, 44, 59, 183, 157, 63, 109, 159, 73, 40, 231, 28, 196, 249, 48, 211, 73, 157, 194, 99, 17, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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