Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dede5e51f48b68a4b8e252df7dfd3e31dc7f6019b645b309f34585cda9232a14

Tx prefix hash: 581ea69d40159e48998dc8e0cffc6a5d7d1767918892912978a200638596008f
Tx public key: e1f48e7d23e6628b56b161bfba02bfc0065309e93a1224cf0554ec97b9671e9e
Timestamp: 1728804739 Timestamp [UCT]: 2024-10-13 07:32:19 Age [y:d:h:m:s]: 00:103:16:53:54
Block: 1130561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74079 RingCT/type: yes/0
Extra: 01e1f48e7d23e6628b56b161bfba02bfc0065309e93a1224cf0554ec97b9671e9e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b04e9482226af2a0586357fb302fd745e5256a26610d1be2c7cacd0a4b3685b 0.600000000000 1613438 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": 1130571, "vin": [ { "gen": { "height": 1130561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b04e9482226af2a0586357fb302fd745e5256a26610d1be2c7cacd0a4b3685b" } } ], "extra": [ 1, 225, 244, 142, 125, 35, 230, 98, 139, 86, 177, 97, 191, 186, 2, 191, 192, 6, 83, 9, 233, 58, 18, 36, 207, 5, 84, 236, 151, 185, 103, 30, 158, 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