Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a302f9b05020d4810c07ceee7d268309390915dca1bf6a01cee83691c5811b

Tx prefix hash: 422dd5406a130669ac32764e32117b1948e4c74ebb00ba473bba80b07a927d94
Tx public key: 0f505120dd95a6a7c7633228a4c8dc714f911bb804c8a0d2f19ee6f2516feb54
Timestamp: 1745468298 Timestamp [UCT]: 2025-04-24 04:18:18 Age [y:d:h:m:s]: 00:210:03:43:11
Block: 1268190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147917 RingCT/type: yes/0
Extra: 010f505120dd95a6a7c7633228a4c8dc714f911bb804c8a0d2f19ee6f2516feb540211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bba4b4ca4a707c5d6f023338556f109f4be8497e9b218be4035a350bfbfb1e09 0.600000000000 1755419 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": 1268200, "vin": [ { "gen": { "height": 1268190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bba4b4ca4a707c5d6f023338556f109f4be8497e9b218be4035a350bfbfb1e09" } } ], "extra": [ 1, 15, 80, 81, 32, 221, 149, 166, 167, 199, 99, 50, 40, 164, 200, 220, 113, 79, 145, 27, 184, 4, 200, 160, 210, 241, 158, 230, 242, 81, 111, 235, 84, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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