Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b12d7c17157bb4b2fdf6a9e9fc14c3ad79233ad12117374e3139d4082464cba2

Tx prefix hash: 465f88601301203ead679c9f375715fb00dab34cf5bc8efbe94cec12225f6ca4
Tx public key: 3b092093dc21fbfb42d1baea0cd9143b3d1221d8fa84fd34d728348cb8807089
Timestamp: 1749651915 Timestamp [UCT]: 2025-06-11 14:25:15 Age [y:d:h:m:s]: 00:151:07:39:12
Block: 1302814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105843 RingCT/type: yes/0
Extra: 013b092093dc21fbfb42d1baea0cd9143b3d1221d8fa84fd34d728348cb8807089021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99a5b3928015fe9c3500bf242f7a6a3a23b4e8b8a89048563d7a3a18e2823ba0 0.600000000000 1790387 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": 1302824, "vin": [ { "gen": { "height": 1302814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99a5b3928015fe9c3500bf242f7a6a3a23b4e8b8a89048563d7a3a18e2823ba0" } } ], "extra": [ 1, 59, 9, 32, 147, 220, 33, 251, 251, 66, 209, 186, 234, 12, 217, 20, 59, 61, 18, 33, 216, 250, 132, 253, 52, 215, 40, 52, 140, 184, 128, 112, 137, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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