Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d93497149784ed81fd6d7f2c270ad8a795e56ac6f6a1d411e1c460d9c62a91a

Tx prefix hash: 26793c9fdc76b7a97be2884858f60ca32fe214aac0ef156e57656cb6f9c5931b
Tx public key: 4bf1dba92c542a0394541d04946b38b91a991b678d82fb03e612936b3e822f83
Timestamp: 1707431053 Timestamp [UCT]: 2024-02-08 22:24:13 Age [y:d:h:m:s]: 00:362:19:09:13
Block: 953340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259453 RingCT/type: yes/0
Extra: 014bf1dba92c542a0394541d04946b38b91a991b678d82fb03e612936b3e822f8302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 484df9e7411c068a6d307172fb262af74d59215168860d4cdd301783306dd150 0.600000000000 1412534 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": 953350, "vin": [ { "gen": { "height": 953340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "484df9e7411c068a6d307172fb262af74d59215168860d4cdd301783306dd150" } } ], "extra": [ 1, 75, 241, 219, 169, 44, 84, 42, 3, 148, 84, 29, 4, 148, 107, 56, 185, 26, 153, 27, 103, 141, 130, 251, 3, 230, 18, 147, 107, 62, 130, 47, 131, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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