Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e393202923f5e840a1f208bba650f891b6b97258c1659d0481ef641145b0cd8

Tx prefix hash: d40f27c497771ca6fb32e43c8069b164869d8c3311f88c0873681602b356fd78
Tx public key: 44bc0ca080b939b0f39b3c274df60b5a6f20ef38f27f3af8412237cd40dc26a6
Timestamp: 1751795557 Timestamp [UCT]: 2025-07-06 09:52:37 Age [y:d:h:m:s]: 00:136:22:08:52
Block: 1319853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96254 RingCT/type: yes/0
Extra: 0144bc0ca080b939b0f39b3c274df60b5a6f20ef38f27f3af8412237cd40dc26a6021100000006d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4148e3c491393fc1476863120045e216c2db204ce592d85dc6c6590d58dd7b9 0.600000000000 1807546 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": 1319863, "vin": [ { "gen": { "height": 1319853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4148e3c491393fc1476863120045e216c2db204ce592d85dc6c6590d58dd7b9" } } ], "extra": [ 1, 68, 188, 12, 160, 128, 185, 57, 176, 243, 155, 60, 39, 77, 246, 11, 90, 111, 32, 239, 56, 242, 127, 58, 248, 65, 34, 55, 205, 64, 220, 38, 166, 2, 17, 0, 0, 0, 6, 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