Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 305a01d8f9f1ed6f2179c9ce77a10b1ea6f327dda55a19924a39977f8a869615

Tx prefix hash: 2c04ff600681d993b9cbca6c6a4342ebf399f10e6d1dbfb37e3438b114387f48
Tx public key: 9be6d20f15e3fac72ed8b20613ce53732c72ee35000e42b86488b8a3a0b734e3
Timestamp: 1749409392 Timestamp [UCT]: 2025-06-08 19:03:12 Age [y:d:h:m:s]: 00:157:17:22:52
Block: 1300825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110402 RingCT/type: yes/0
Extra: 019be6d20f15e3fac72ed8b20613ce53732c72ee35000e42b86488b8a3a0b734e3021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a70f0af2d7c72285806549750f2938b00345f041d9e0ef813d562895cdebc6e 0.600000000000 1788376 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": 1300835, "vin": [ { "gen": { "height": 1300825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a70f0af2d7c72285806549750f2938b00345f041d9e0ef813d562895cdebc6e" } } ], "extra": [ 1, 155, 230, 210, 15, 21, 227, 250, 199, 46, 216, 178, 6, 19, 206, 83, 115, 44, 114, 238, 53, 0, 14, 66, 184, 100, 136, 184, 163, 160, 183, 52, 227, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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