Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d4e003d6173872ba86529dbf0f6e4939b100f70e0d882f35b2ef676a7488f21

Tx prefix hash: 4a3cde03130a75df5c92ae0da1280eac19f95e1826784cd4189da303ca0aba51
Tx public key: 04ff16f613abe0c2d66f4ee7e88fb64992505351054aef584a2ae80afea07f99
Timestamp: 1728226606 Timestamp [UCT]: 2024-10-06 14:56:46 Age [y:d:h:m:s]: 00:192:14:44:36
Block: 1125760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137453 RingCT/type: yes/0
Extra: 0104ff16f613abe0c2d66f4ee7e88fb64992505351054aef584a2ae80afea07f9902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83538907851bc7b56dbaa025165ee12e66d2c0623b2d4ea0269213d91cb06d6d 0.600000000000 1608511 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": 1125770, "vin": [ { "gen": { "height": 1125760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83538907851bc7b56dbaa025165ee12e66d2c0623b2d4ea0269213d91cb06d6d" } } ], "extra": [ 1, 4, 255, 22, 246, 19, 171, 224, 194, 214, 111, 78, 231, 232, 143, 182, 73, 146, 80, 83, 81, 5, 74, 239, 88, 74, 42, 232, 10, 254, 160, 127, 153, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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