Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 298eabda01d8422c3ec0b1bd5a7b78c1623a75f7d544b53228acb015d46ed092

Tx prefix hash: 2eacea0dec36290cc8f675d372806e8e36c506b840580dac31e9ac854209aa94
Tx public key: c57943bea8e0ee91d36603033c815c101a450608ae31698a45e8a4ad7c48963a
Timestamp: 1749700633 Timestamp [UCT]: 2025-06-12 03:57:13 Age [y:d:h:m:s]: 00:157:15:31:10
Block: 1303204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110379 RingCT/type: yes/0
Extra: 01c57943bea8e0ee91d36603033c815c101a450608ae31698a45e8a4ad7c48963a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a1efc8e71a54b2638f0ae4ee99d5290b5e4640b868e4873eb3ea9dd4fdb5a66 0.600000000000 1790781 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": 1303214, "vin": [ { "gen": { "height": 1303204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a1efc8e71a54b2638f0ae4ee99d5290b5e4640b868e4873eb3ea9dd4fdb5a66" } } ], "extra": [ 1, 197, 121, 67, 190, 168, 224, 238, 145, 211, 102, 3, 3, 60, 129, 92, 16, 26, 69, 6, 8, 174, 49, 105, 138, 69, 232, 164, 173, 124, 72, 150, 58, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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