Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b768dc943b0c575775b1902f2a614622db51edcf014c1a6181b4e0bb422daa

Tx prefix hash: bd5673989430bd5bc2c102a97be43ee633ea10b021cf3800f0af46c2ebfabf9f
Tx public key: ae1752639dc363e6a5fbeddd5cef091a6373c05e0140610ae93a3bd48bb511c5
Timestamp: 1723065755 Timestamp [UCT]: 2024-08-07 21:22:35 Age [y:d:h:m:s]: 01:104:04:52:49
Block: 1082969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332968 RingCT/type: yes/0
Extra: 01ae1752639dc363e6a5fbeddd5cef091a6373c05e0140610ae93a3bd48bb511c502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c31f586fd0af97f65dc89451fa772f36ad7fa8311059e9a9ae3c0a6634da04b 0.600000000000 1556804 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": 1082979, "vin": [ { "gen": { "height": 1082969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c31f586fd0af97f65dc89451fa772f36ad7fa8311059e9a9ae3c0a6634da04b" } } ], "extra": [ 1, 174, 23, 82, 99, 157, 195, 99, 230, 165, 251, 237, 221, 92, 239, 9, 26, 99, 115, 192, 94, 1, 64, 97, 10, 233, 58, 59, 212, 139, 181, 17, 197, 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