Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a28d895550e45e24a0aaea1e9fbbddcf099268d66df6e2de37d4840d2763173

Tx prefix hash: a79c1acab8700fff3deba2d0279bba2004321af20c35763a77007f2c815aed00
Tx public key: ab64642f4b1fa241c881f262a463178e06a16e35c2aff7f4a6f8fae82847cfed
Timestamp: 1752612151 Timestamp [UCT]: 2025-07-15 20:42:31 Age [y:d:h:m:s]: 00:133:17:37:05
Block: 1326254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94336 RingCT/type: yes/0
Extra: 01ab64642f4b1fa241c881f262a463178e06a16e35c2aff7f4a6f8fae82847cfed0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01a82efc64587b4a13f08f0a69ca93c88afe9f1f12a8f15b142b6e6c4b4ba90b 0.600000000000 1814005 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": 1326264, "vin": [ { "gen": { "height": 1326254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01a82efc64587b4a13f08f0a69ca93c88afe9f1f12a8f15b142b6e6c4b4ba90b" } } ], "extra": [ 1, 171, 100, 100, 47, 75, 31, 162, 65, 200, 129, 242, 98, 164, 99, 23, 142, 6, 161, 110, 53, 194, 175, 247, 244, 166, 248, 250, 232, 40, 71, 207, 237, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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