Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389d4803ff4ada38b37c7a02f9db4c6c268e80f9a8662628f797fa59244fd3ea

Tx prefix hash: 32334ca24191c2b73d31178b324615589dd4fe5350b8bed5746b16258dc3580b
Tx public key: a8292b6515fa0d3e68bb45d261cbdee5f3dc99f7490549c64166db899b8437e6
Timestamp: 1734986388 Timestamp [UCT]: 2024-12-23 20:39:48 Age [y:d:h:m:s]: 00:311:15:10:56
Block: 1181717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220193 RingCT/type: yes/0
Extra: 01a8292b6515fa0d3e68bb45d261cbdee5f3dc99f7490549c64166db899b8437e60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 871e7526f6a671ea8cfca61509e09f367eb215708441d93ea64b34c4a25170cc 0.600000000000 1668142 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": 1181727, "vin": [ { "gen": { "height": 1181717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "871e7526f6a671ea8cfca61509e09f367eb215708441d93ea64b34c4a25170cc" } } ], "extra": [ 1, 168, 41, 43, 101, 21, 250, 13, 62, 104, 187, 69, 210, 97, 203, 222, 229, 243, 220, 153, 247, 73, 5, 73, 198, 65, 102, 219, 137, 155, 132, 55, 230, 2, 17, 0, 0, 0, 2, 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