Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0c6a1df537bea932e287a86f69930c7d9082eea7280eb24789fc083ecb40f8d

Tx prefix hash: b6617166c6f10692d4172740573bef29bb471a09380ab355ec5fd261102b2340
Tx public key: 565c1e7976b399468fa76c149f84f4c9ee4a5bc8141495dd12b0f7dc65a9fbae
Timestamp: 1764738671 Timestamp [UCT]: 2025-12-03 05:11:11 Age [y:d:h:m:s]: 00:000:21:38:59
Block: 1425327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647 RingCT/type: yes/0
Extra: 01565c1e7976b399468fa76c149f84f4c9ee4a5bc8141495dd12b0f7dc65a9fbae021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c415d0a9265f356a647f7da793690b2e08b54394aa30dcad8fea7b5e0b6f89c 0.600000000000 1913960 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": 1425337, "vin": [ { "gen": { "height": 1425327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c415d0a9265f356a647f7da793690b2e08b54394aa30dcad8fea7b5e0b6f89c" } } ], "extra": [ 1, 86, 92, 30, 121, 118, 179, 153, 70, 143, 167, 108, 20, 159, 132, 244, 201, 238, 74, 91, 200, 20, 20, 149, 221, 18, 176, 247, 220, 101, 169, 251, 174, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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