Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 784491bec2bff78d9f0c4cca4d3942cf44edca87f2a4de508c2d4bf10eb9fe60

Tx prefix hash: 296b8ca45837d8aa05a6b4b1e9a1b790dded0a39de18e7b2c28cc3b5aef826b3
Tx public key: 03e1629a4f015ef49e5d55401a45f3df0678c761b4a37e6caf00a4db4aa8ee05
Timestamp: 1756118938 Timestamp [UCT]: 2025-08-25 10:48:58 Age [y:d:h:m:s]: 00:087:20:56:26
Block: 1354081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62719 RingCT/type: yes/0
Extra: 0103e1629a4f015ef49e5d55401a45f3df0678c761b4a37e6caf00a4db4aa8ee050211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a45717025528515283605d4b005f32e9b4c9a6f04be28ca6ee96d6f520ee8843 0.600000000000 1842062 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": 1354091, "vin": [ { "gen": { "height": 1354081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a45717025528515283605d4b005f32e9b4c9a6f04be28ca6ee96d6f520ee8843" } } ], "extra": [ 1, 3, 225, 98, 154, 79, 1, 94, 244, 158, 93, 85, 64, 26, 69, 243, 223, 6, 120, 199, 97, 180, 163, 126, 108, 175, 0, 164, 219, 74, 168, 238, 5, 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