Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3daea5dce4e9fda780a4174467c7e6734e520883fddbc21b962dcdbc5b70cb61

Tx prefix hash: a7430e0b7667cf07df609b5718acc96783aeb84915ce0a75a6f0a5c4f4e493ca
Tx public key: f92778c6e6f4e542971c3a81930f71dd1ed3baec11f25b027968f80332795377
Timestamp: 1700925153 Timestamp [UCT]: 2023-11-25 15:12:33 Age [y:d:h:m:s]: 01:096:07:35:47
Block: 899418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329968 RingCT/type: yes/0
Extra: 01f92778c6e6f4e542971c3a81930f71dd1ed3baec11f25b027968f80332795377021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.642472856000 dcy

stealth address amount amount idx
00: 9c79d4133a56fe8dfbd296a62c366899f14618c4e6280279dbd75d28d5ed2721 0.642472856000 1355873 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": 899428, "vin": [ { "gen": { "height": 899418 } } ], "vout": [ { "amount": 642472856, "target": { "key": "9c79d4133a56fe8dfbd296a62c366899f14618c4e6280279dbd75d28d5ed2721" } } ], "extra": [ 1, 249, 39, 120, 198, 230, 244, 229, 66, 151, 28, 58, 129, 147, 15, 113, 221, 30, 211, 186, 236, 17, 242, 91, 2, 121, 104, 248, 3, 50, 121, 83, 119, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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