Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a2be212021d96388165744ed3c42de015f1b8300700b4a038246f974046a9d0

Tx prefix hash: a17f1c0aa3830d666eaa8b05f9febb5936e3e0462783056675239007649eeeb1
Tx public key: 9545c6bb7d6a705e772b407cc0f50f5c07a201ada3d8bc46bb2e20eb259f058e
Timestamp: 1763478387 Timestamp [UCT]: 2025-11-18 15:06:27 Age [y:d:h:m:s]: 00:009:15:31:57
Block: 1414885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6906 RingCT/type: yes/0
Extra: 019545c6bb7d6a705e772b407cc0f50f5c07a201ada3d8bc46bb2e20eb259f058e0211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a845c53221ebb2d5a834093027e8b8c6e738e1df46c9a2a4d2c44c5a02385f36 0.600000000000 1903378 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": 1414895, "vin": [ { "gen": { "height": 1414885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a845c53221ebb2d5a834093027e8b8c6e738e1df46c9a2a4d2c44c5a02385f36" } } ], "extra": [ 1, 149, 69, 198, 187, 125, 106, 112, 94, 119, 43, 64, 124, 192, 245, 15, 92, 7, 162, 1, 173, 163, 216, 188, 70, 187, 46, 32, 235, 37, 159, 5, 142, 2, 17, 0, 0, 0, 2, 140, 235, 127, 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