Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b9b8e9d1ac3fa27c2223ab7a921a5b11ff875389cd0030964b71130700b5c8d

Tx prefix hash: d79ba105e7b6c8fd0848060832dbc05b46f071aa309f920a03edfc5911ed5af5
Tx public key: 8541e5aa0fe629ecf8d135854e879ac45ba0265508a0de22af9dc0016ad1e1fe
Timestamp: 1763028072 Timestamp [UCT]: 2025-11-13 10:01:12 Age [y:d:h:m:s]: 00:014:19:54:11
Block: 1411158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10614 RingCT/type: yes/0
Extra: 018541e5aa0fe629ecf8d135854e879ac45ba0265508a0de22af9dc0016ad1e1fe021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8659baeb0d8a5f2623d5cae9e90532eac2942bf72a8b316b25cfa80439c826a8 0.600000000000 1899615 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": 1411168, "vin": [ { "gen": { "height": 1411158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8659baeb0d8a5f2623d5cae9e90532eac2942bf72a8b316b25cfa80439c826a8" } } ], "extra": [ 1, 133, 65, 229, 170, 15, 230, 41, 236, 248, 209, 53, 133, 78, 135, 154, 196, 91, 160, 38, 85, 8, 160, 222, 34, 175, 157, 192, 1, 106, 209, 225, 254, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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