Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1ac3e4f60bc425cbec6ffae684cc5772e0fe15dc921b91209b0bd3f626c4571

Tx prefix hash: df79118491c3f393ada13906e36c56a962b5b8aa68728f61407fefe9ba52d60d
Tx public key: 473c329651465a635ddd7a23b909fb5b2a4b7346f32fd91094faf21b2a872ca1
Timestamp: 1730877654 Timestamp [UCT]: 2024-11-06 07:20:54 Age [y:d:h:m:s]: 00:001:05:19:25
Block: 1147644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 885 RingCT/type: yes/0
Extra: 01473c329651465a635ddd7a23b909fb5b2a4b7346f32fd91094faf21b2a872ca1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ed1dd3ba7f300ef709f1d49120e1ab9fb0bb55770265e38aa434989414f8faf 0.600000000000 1632343 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": 1147654, "vin": [ { "gen": { "height": 1147644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ed1dd3ba7f300ef709f1d49120e1ab9fb0bb55770265e38aa434989414f8faf" } } ], "extra": [ 1, 71, 60, 50, 150, 81, 70, 90, 99, 93, 221, 122, 35, 185, 9, 251, 91, 42, 75, 115, 70, 243, 47, 217, 16, 148, 250, 242, 27, 42, 135, 44, 161, 2, 17, 0, 0, 0, 1, 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