Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36de455aff393d18db4f3a12c514c28a3b6155168926c7c1192bc19006118513

Tx prefix hash: bf4e482f19f88faa7dffd8d8d7ae4ec33e8690ded0dcc016199727d63725bf7e
Tx public key: 1354b28af91c35d38e6cde97e13d92d1fce39e4dad50f9c4c6cbe9556337f6b9
Timestamp: 1723970397 Timestamp [UCT]: 2024-08-18 08:39:57 Age [y:d:h:m:s]: 00:235:03:16:54
Block: 1090477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167922 RingCT/type: yes/0
Extra: 011354b28af91c35d38e6cde97e13d92d1fce39e4dad50f9c4c6cbe9556337f6b902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 173226bed3631a0b7f03fd077846d2963aaf2f25437b80c4eb9014d9e9c0110d 0.600000000000 1565100 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": 1090487, "vin": [ { "gen": { "height": 1090477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "173226bed3631a0b7f03fd077846d2963aaf2f25437b80c4eb9014d9e9c0110d" } } ], "extra": [ 1, 19, 84, 178, 138, 249, 28, 53, 211, 142, 108, 222, 151, 225, 61, 146, 209, 252, 227, 158, 77, 173, 80, 249, 196, 198, 203, 233, 85, 99, 55, 246, 185, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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