Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2acbaeaa74cb0f9b401b86807a6ddd8542fb82a29b17f04f3384975dba3794a9

Tx prefix hash: 3d5afb0c9d45293f053a24586e815dcc2e95bfc5c3b32222b48e4186142a80b8
Tx public key: 8605608fc0b8de30e85d7709625bd00ef4ef60f9daf94845df59e674eb73111e
Timestamp: 1761737552 Timestamp [UCT]: 2025-10-29 11:32:32 Age [y:d:h:m:s]: 00:092:01:04:20
Block: 1400472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65712 RingCT/type: yes/0
Extra: 018605608fc0b8de30e85d7709625bd00ef4ef60f9daf94845df59e674eb73111e0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d15e7bdb341acc49b4af2352dbc72e8b139f05df417ae39c223514a5cb16f57 0.600000000000 1888781 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": 1400482, "vin": [ { "gen": { "height": 1400472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d15e7bdb341acc49b4af2352dbc72e8b139f05df417ae39c223514a5cb16f57" } } ], "extra": [ 1, 134, 5, 96, 143, 192, 184, 222, 48, 232, 93, 119, 9, 98, 91, 208, 14, 244, 239, 96, 249, 218, 249, 72, 69, 223, 89, 230, 116, 235, 115, 17, 30, 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