Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8fe4d3b01b90ab0e577c3cb19102f0460d95038934b36cc7bfce3c143687a42

Tx prefix hash: a9f3cf2ab6fef4fd8a0969cde19ea185ef5ed83e3dc2921ee77d1410dde78cb2
Tx public key: b9bfddc32c9ded3bce1efb496aa31110a4680ddc602ef7c62bf07bc7611c52a4
Timestamp: 1717839061 Timestamp [UCT]: 2024-06-08 09:31:01 Age [y:d:h:m:s]: 00:284:06:08:01
Block: 1039642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203146 RingCT/type: yes/0
Extra: 01b9bfddc32c9ded3bce1efb496aa31110a4680ddc602ef7c62bf07bc7611c52a402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c9a14d8df8c6ffd310fae73f3fa1298ff287f5b98109ffc499a1a0bbada4a01 0.600000000000 1508289 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": 1039652, "vin": [ { "gen": { "height": 1039642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c9a14d8df8c6ffd310fae73f3fa1298ff287f5b98109ffc499a1a0bbada4a01" } } ], "extra": [ 1, 185, 191, 221, 195, 44, 157, 237, 59, 206, 30, 251, 73, 106, 163, 17, 16, 164, 104, 13, 220, 96, 46, 247, 198, 43, 240, 123, 199, 97, 28, 82, 164, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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