Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea523114cc1ead5638d4329947e7089a52ac8ca83cc181b8450357b4b7984aed

Tx prefix hash: 57a6499d13f9eb6f744552a2cc4f37ce59a4b259208f42a1ea53e6d9cdf1242c
Tx public key: 430ae89785f83ae2c8aac640cb0c4442b78e686660c7f7a6e34b47f354eb3387
Timestamp: 1708072224 Timestamp [UCT]: 2024-02-16 08:30:24 Age [y:d:h:m:s]: 01:044:19:07:48
Block: 958659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293047 RingCT/type: yes/0
Extra: 01430ae89785f83ae2c8aac640cb0c4442b78e686660c7f7a6e34b47f354eb338702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7066b467eebdec8f49e5e8a7932ca995d073279ec09659f85be921c0ba83d1cc 0.600000000000 1418018 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": 958669, "vin": [ { "gen": { "height": 958659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7066b467eebdec8f49e5e8a7932ca995d073279ec09659f85be921c0ba83d1cc" } } ], "extra": [ 1, 67, 10, 232, 151, 133, 248, 58, 226, 200, 170, 198, 64, 203, 12, 68, 66, 183, 142, 104, 102, 96, 199, 247, 166, 227, 75, 71, 243, 84, 235, 51, 135, 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