Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d7e9f6364266398fb419f71fe61efdb27a147763c851dc813328f78411947f7

Tx prefix hash: d9ac6528f0bc758250b4c438bb0567f3ae004d83e7c98a3dd198dbb7cea029cc
Tx public key: 9f7b36def6980cf3a2cc83793e2e2bd83cfdcb17716c9d9f88d3ee87163b786a
Timestamp: 1724636583 Timestamp [UCT]: 2024-08-26 01:43:03 Age [y:d:h:m:s]: 00:227:12:38:30
Block: 1095982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162491 RingCT/type: yes/0
Extra: 019f7b36def6980cf3a2cc83793e2e2bd83cfdcb17716c9d9f88d3ee87163b786a02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f91cecea463183d8c09382bb6b4c7a24fc14f656de0adfa4f7eea687ccff09ba 0.600000000000 1571169 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": 1095992, "vin": [ { "gen": { "height": 1095982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f91cecea463183d8c09382bb6b4c7a24fc14f656de0adfa4f7eea687ccff09ba" } } ], "extra": [ 1, 159, 123, 54, 222, 246, 152, 12, 243, 162, 204, 131, 121, 62, 46, 43, 216, 60, 253, 203, 23, 113, 108, 157, 159, 136, 211, 238, 135, 22, 59, 120, 106, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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