Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9093e6f6e4bf57ce2e9d9995c7bf98f3dbfc8ae9f54d1f3b1a7374e29fa07d1c

Tx prefix hash: a5ec98798b2c39c49c9e9e3fb033c1fc41ec5e1e2aa4e1f45cb08bd566ca3afc
Tx public key: a01082ba33ad3778f6dca8a30b9c6abffb4b333a3b14c3871edb74903d6c90a0
Timestamp: 1760403087 Timestamp [UCT]: 2025-10-14 00:51:27 Age [y:d:h:m:s]: 00:107:13:06:35
Block: 1389409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76811 RingCT/type: yes/0
Extra: 01a01082ba33ad3778f6dca8a30b9c6abffb4b333a3b14c3871edb74903d6c90a0021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41c735d7b4834c104c1fbd85dcc1eb9cc01f9e2f38c1c741d43a74360f80753c 0.600000000000 1877638 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": 1389419, "vin": [ { "gen": { "height": 1389409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c735d7b4834c104c1fbd85dcc1eb9cc01f9e2f38c1c741d43a74360f80753c" } } ], "extra": [ 1, 160, 16, 130, 186, 51, 173, 55, 120, 246, 220, 168, 163, 11, 156, 106, 191, 251, 75, 51, 58, 59, 20, 195, 135, 30, 219, 116, 144, 61, 108, 144, 160, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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