Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9006b03ff9ee726d68cd306a9ae25ba1542b3156ee4694bb52cda4837d11bf8a

Tx prefix hash: aebb92b398c951c0d955120ade3070eaca0fef62b40eddbff5d478bc6ad9a060
Tx public key: e0b288b9979d5083e8c9afccde9711868a6a3c67cda5dcbeaf9d73c8ed3d0c9b
Timestamp: 1741813780 Timestamp [UCT]: 2025-03-12 21:09:40 Age [y:d:h:m:s]: 00:300:14:59:17
Block: 1237942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212664 RingCT/type: yes/0
Extra: 01e0b288b9979d5083e8c9afccde9711868a6a3c67cda5dcbeaf9d73c8ed3d0c9b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af263a31cb9c63b1014364c916657d3c27f62aa6ca97b5730eb208e7f1a0adea 0.600000000000 1724901 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": 1237952, "vin": [ { "gen": { "height": 1237942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af263a31cb9c63b1014364c916657d3c27f62aa6ca97b5730eb208e7f1a0adea" } } ], "extra": [ 1, 224, 178, 136, 185, 151, 157, 80, 131, 232, 201, 175, 204, 222, 151, 17, 134, 138, 106, 60, 103, 205, 165, 220, 190, 175, 157, 115, 200, 237, 61, 12, 155, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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