Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2a0814444ef4ad0917991ab17cc71a087504e18c831c006bcb83d67405a23af

Tx prefix hash: 254ad0a909221ecf6de2fcb358ef53e2e3b0d5df7cda354142e5e3ef8c23f0ec
Tx public key: 1f878ff80243a05d89cbd0e3373707df2f75ef184e542f67142e12ace92fff3b
Timestamp: 1736490187 Timestamp [UCT]: 2025-01-10 06:23:07 Age [y:d:h:m:s]: 00:098:09:50:09
Block: 1194133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70119 RingCT/type: yes/0
Extra: 011f878ff80243a05d89cbd0e3373707df2f75ef184e542f67142e12ace92fff3b0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0630acec89d9b07da64a87f3a77e69214f257cb2907fdae3a4b0f298e5be909 0.600000000000 1680700 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": 1194143, "vin": [ { "gen": { "height": 1194133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0630acec89d9b07da64a87f3a77e69214f257cb2907fdae3a4b0f298e5be909" } } ], "extra": [ 1, 31, 135, 143, 248, 2, 67, 160, 93, 137, 203, 208, 227, 55, 55, 7, 223, 47, 117, 239, 24, 78, 84, 47, 103, 20, 46, 18, 172, 233, 47, 255, 59, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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