Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59920207c877852dbb6576cad98998a1d38bb4f124a9bded766822f40e27652a

Tx prefix hash: 768644225b35e9726111ee8a571c3289f21578f5a77e58573375bf4bf549d33b
Tx public key: a7fb23d8c052227c80c9adf220329e5d7c9e69fbd0c3733e13d8d011bd684796
Timestamp: 1580382753 Timestamp [UCT]: 2020-01-30 11:12:33 Age [y:d:h:m:s]: 04:305:01:52:53
Block: 55391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108903 RingCT/type: yes/0
Extra: 01a7fb23d8c052227c80c9adf220329e5d7c9e69fbd0c3733e13d8d011bd6847960211000000014943cd9f000000000000000000

1 output(s) for total of 402.223506881000 dcy

stealth address amount amount idx
00: cc536f8117ca54b649238bde167a08325a7744aa4c0b9de70187591a5e093dc5 402.223506881000 102257 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": 55401, "vin": [ { "gen": { "height": 55391 } } ], "vout": [ { "amount": 402223506881, "target": { "key": "cc536f8117ca54b649238bde167a08325a7744aa4c0b9de70187591a5e093dc5" } } ], "extra": [ 1, 167, 251, 35, 216, 192, 82, 34, 124, 128, 201, 173, 242, 32, 50, 158, 93, 124, 158, 105, 251, 208, 195, 115, 62, 19, 216, 208, 17, 189, 104, 71, 150, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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