Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3483543f3511b8fee5ee071476eead59fea4c9630d7a267d32e655e9f9dbc9ff

Tx prefix hash: 1f99ecbf68f0ad888c775ded1587f514f27977c5c8b1a63d887816d9b6da33a8
Tx public key: be7ebbf8d9c996e8710d5eb08e8c47426663887e5b9e741b0cc695d2204c6fae
Timestamp: 1757984364 Timestamp [UCT]: 2025-09-16 00:59:24 Age [y:d:h:m:s]: 00:109:20:46:50
Block: 1369355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78676 RingCT/type: yes/0
Extra: 01be7ebbf8d9c996e8710d5eb08e8c47426663887e5b9e741b0cc695d2204c6fae021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9168705e9df8a3ce6e1121c619ceb5404dead819a40a05029495de03553e5c44 0.600000000000 1857430 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": 1369365, "vin": [ { "gen": { "height": 1369355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9168705e9df8a3ce6e1121c619ceb5404dead819a40a05029495de03553e5c44" } } ], "extra": [ 1, 190, 126, 187, 248, 217, 201, 150, 232, 113, 13, 94, 176, 142, 140, 71, 66, 102, 99, 136, 126, 91, 158, 116, 27, 12, 198, 149, 210, 32, 76, 111, 174, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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