Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc5ff2f14889c399edd6fab8a3132b562284d72fd69543c0fbb48c1dac902f14

Tx prefix hash: ee06a6d2839c6b0710998b64f4c270806feed0c4678cd81ae067d57668e3d8cd
Tx public key: 6ca512ea6f66d9f7eba12580fa528d197d80b19dc01c145a9a5e0017b3387692
Timestamp: 1717534832 Timestamp [UCT]: 2024-06-04 21:00:32 Age [y:d:h:m:s]: 01:155:22:10:07
Block: 1037123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370009 RingCT/type: yes/0
Extra: 016ca512ea6f66d9f7eba12580fa528d197d80b19dc01c145a9a5e0017b33876920211000000024385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04a1449b82f614b8851d72bb5783e34b671bb5e109a564fe9ce50c387136561 0.600000000000 1505654 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": 1037133, "vin": [ { "gen": { "height": 1037123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04a1449b82f614b8851d72bb5783e34b671bb5e109a564fe9ce50c387136561" } } ], "extra": [ 1, 108, 165, 18, 234, 111, 102, 217, 247, 235, 161, 37, 128, 250, 82, 141, 25, 125, 128, 177, 157, 192, 28, 20, 90, 154, 94, 0, 23, 179, 56, 118, 146, 2, 17, 0, 0, 0, 2, 67, 133, 54, 42, 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