Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0e4f922fbbf5b3f237ff34a920d96c8aeb91a1a331b62fa73b2afedbd352449

Tx prefix hash: 65c38f9e8fe3e75e3ba19433e299881fcc7273491f704ae4146a673b2741bdfe
Tx public key: f72061539234a25346c65434a6e4c89535238bba3724cbb43a11f302fb28291c
Timestamp: 1711204212 Timestamp [UCT]: 2024-03-23 14:30:12 Age [y:d:h:m:s]: 00:357:20:28:36
Block: 984656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255847 RingCT/type: yes/0
Extra: 01f72061539234a25346c65434a6e4c89535238bba3724cbb43a11f302fb28291c02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b673b0df13d64d0962ac627d1a25c9a67dd120e38c23d1ce3df6bd18bdc8aec 0.600000000000 1444829 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": 984666, "vin": [ { "gen": { "height": 984656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b673b0df13d64d0962ac627d1a25c9a67dd120e38c23d1ce3df6bd18bdc8aec" } } ], "extra": [ 1, 247, 32, 97, 83, 146, 52, 162, 83, 70, 198, 84, 52, 166, 228, 200, 149, 53, 35, 139, 186, 55, 36, 203, 180, 58, 17, 243, 2, 251, 40, 41, 28, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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