Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a20da203900af4b7a5f657adabdc4b9ab4c90ec1240246ced9a719912e783ac8

Tx prefix hash: 1f223831a924734e288491d34ef1c7520b0e68782e55f2113c0ad91c8c4af056
Tx public key: 5be46d6d2fa52fed96bec5e84df86c21e87ee8c375e7ab1cb30617f4da127d68
Timestamp: 1695643612 Timestamp [UCT]: 2023-09-25 12:06:52 Age [y:d:h:m:s]: 01:194:23:12:00
Block: 855824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400405 RingCT/type: yes/0
Extra: 015be46d6d2fa52fed96bec5e84df86c21e87ee8c375e7ab1cb30617f4da127d68021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.895983200000 dcy

stealth address amount amount idx
00: d7fe87c988a03d57e1e6511755dbfbc3e86e8888f6e8dcc10b69fa17433475a4 0.895983200000 1309868 of 0

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": 855834, "vin": [ { "gen": { "height": 855824 } } ], "vout": [ { "amount": 895983200, "target": { "key": "d7fe87c988a03d57e1e6511755dbfbc3e86e8888f6e8dcc10b69fa17433475a4" } } ], "extra": [ 1, 91, 228, 109, 109, 47, 165, 47, 237, 150, 190, 197, 232, 77, 248, 108, 33, 232, 126, 232, 195, 117, 231, 171, 28, 179, 6, 23, 244, 218, 18, 125, 104, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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