Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 677c6c4bd89a3f13a6034ccc70076292b591e5a79149bd902a6789bbcc223901

Tx prefix hash: 87c9377f87cf26109b0c495d6347526f19b49a99155d25346501fedf3fee8b51
Tx public key: f62d208097c6358794d2154ada44aaf89bf1dfcf4d2ebef4defb8f0295e4629e
Timestamp: 1587353812 Timestamp [UCT]: 2020-04-20 03:36:52 Age [y:d:h:m:s]: 05:199:05:44:34
Block: 94353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1310344 RingCT/type: yes/0
Extra: 01f62d208097c6358794d2154ada44aaf89bf1dfcf4d2ebef4defb8f0295e4629e0211000001186fa03929000000000000000000

1 output(s) for total of 298.792789182000 dcy

stealth address amount amount idx
00: e35213a7b513d01c5dee7a5702d6703a254a70ce9ed999c2296dbcdae659bda7 298.792789182000 167807 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": 94363, "vin": [ { "gen": { "height": 94353 } } ], "vout": [ { "amount": 298792789182, "target": { "key": "e35213a7b513d01c5dee7a5702d6703a254a70ce9ed999c2296dbcdae659bda7" } } ], "extra": [ 1, 246, 45, 32, 128, 151, 198, 53, 135, 148, 210, 21, 74, 218, 68, 170, 248, 155, 241, 223, 207, 77, 46, 190, 244, 222, 251, 143, 2, 149, 228, 98, 158, 2, 17, 0, 0, 1, 24, 111, 160, 57, 41, 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