Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee61fbe1804d807fdd027413855ffb069b2499e33ef30ecbd0c3dc540deea36

Tx prefix hash: 3df282da94e5ce05581fdd4c60e5d12160b0907c5a1cff0a58b905bcc6b12708
Tx public key: 19105ec53c5abacafa3bde7db2c4e9d829d73217e003d27a738682e30e8b823b
Timestamp: 1763544409 Timestamp [UCT]: 2025-11-19 09:26:49 Age [y:d:h:m:s]: 00:008:20:59:00
Block: 1415425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6362 RingCT/type: yes/0
Extra: 0119105ec53c5abacafa3bde7db2c4e9d829d73217e003d27a738682e30e8b823b02110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9da936b11e13a7de052c4d8df1649c694e7e1a552a73e1373196d44ffdc5a702 0.600000000000 1903926 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": 1415435, "vin": [ { "gen": { "height": 1415425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9da936b11e13a7de052c4d8df1649c694e7e1a552a73e1373196d44ffdc5a702" } } ], "extra": [ 1, 25, 16, 94, 197, 60, 90, 186, 202, 250, 59, 222, 125, 178, 196, 233, 216, 41, 215, 50, 23, 224, 3, 210, 122, 115, 134, 130, 227, 14, 139, 130, 59, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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