Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d7cf382302051f99d51ac623d6588681daf996a6bdef9579a7affa8d0694214

Tx prefix hash: d3b28ef3f78b039e3bf2fb89aca16f63476acb64642d44b44135c7e389ea8372
Tx public key: 01b934cff597fee21839c6de0b93c2b27844f8e087f9c350b486c4e1013fbffe
Timestamp: 1672802960 Timestamp [UCT]: 2023-01-04 03:29:20 Age [y:d:h:m:s]: 02:012:11:22:06
Block: 667145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530806 RingCT/type: yes/0
Extra: 0101b934cff597fee21839c6de0b93c2b27844f8e087f9c350b486c4e1013fbffe02110000000252542ceb000000000000000000

1 output(s) for total of 3.779824462000 dcy

stealth address amount amount idx
00: bbc1fe179989b1a381f767deeba44712f5c49fdc0b93cc99e6c7e87f339ac5e4 3.779824462000 1108310 of 0

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": 667155, "vin": [ { "gen": { "height": 667145 } } ], "vout": [ { "amount": 3779824462, "target": { "key": "bbc1fe179989b1a381f767deeba44712f5c49fdc0b93cc99e6c7e87f339ac5e4" } } ], "extra": [ 1, 1, 185, 52, 207, 245, 151, 254, 226, 24, 57, 198, 222, 11, 147, 194, 178, 120, 68, 248, 224, 135, 249, 195, 80, 180, 134, 196, 225, 1, 63, 191, 254, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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