Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13ca731a6c06b95494775d764208ae8ad5e6528787f809b5e508de795336edde

Tx prefix hash: c064d320f00f90cbd6d86867d2b4bb186cf9d7716c032f645cf51e484b2e78f3
Tx public key: 8474638f1c4e9b91e691fbd3f621fd4ae6dc1c279e2ef4d87c9fd06d344f8174
Timestamp: 1751285578 Timestamp [UCT]: 2025-06-30 12:12:58 Age [y:d:h:m:s]: 00:136:11:44:41
Block: 1315836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95741 RingCT/type: yes/0
Extra: 018474638f1c4e9b91e691fbd3f621fd4ae6dc1c279e2ef4d87c9fd06d344f8174021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73905e0cf08bf752512022bbbf697e15e18b923ebb4abaac52287f7b1b3aa7b7 0.600000000000 1803493 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": 1315846, "vin": [ { "gen": { "height": 1315836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73905e0cf08bf752512022bbbf697e15e18b923ebb4abaac52287f7b1b3aa7b7" } } ], "extra": [ 1, 132, 116, 99, 143, 28, 78, 155, 145, 230, 145, 251, 211, 246, 33, 253, 74, 230, 220, 28, 39, 158, 46, 244, 216, 124, 159, 208, 109, 52, 79, 129, 116, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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