Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19637afc89183a9599e0d6b0344d86b1374b80b4a00ab172b7a229095a778cb4

Tx prefix hash: 21d8563eea985afc3e698e2c8a990784f41fedad8c757989876d3640428fb407
Tx public key: 02084ee6dae625efabf863c16fe8b52addaf9939ceb9e074c9012a0a365f0e22
Timestamp: 1708761068 Timestamp [UCT]: 2024-02-24 07:51:08 Age [y:d:h:m:s]: 01:027:11:12:20
Block: 964381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280648 RingCT/type: yes/0
Extra: 0102084ee6dae625efabf863c16fe8b52addaf9939ceb9e074c9012a0a365f0e2202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0f2c9b2e69a1c1e51e5dace082cca051acc40ba929a2c1c173397a903ee08d5 0.600000000000 1424112 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": 964391, "vin": [ { "gen": { "height": 964381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0f2c9b2e69a1c1e51e5dace082cca051acc40ba929a2c1c173397a903ee08d5" } } ], "extra": [ 1, 2, 8, 78, 230, 218, 230, 37, 239, 171, 248, 99, 193, 111, 232, 181, 42, 221, 175, 153, 57, 206, 185, 224, 116, 201, 1, 42, 10, 54, 95, 14, 34, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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