Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 988333c84e711b6f0fcf4bcd4b06629a37787b851c7aed6851928da713839973

Tx prefix hash: 1c90fe349bec569830e5dd7430322a7c1fe4d4169ae5fb18ab64c831edcd217a
Tx public key: 93684a6f8a51d3d6b87ac1796c0311017da6e3798411a04f97d2b97ebc057399
Timestamp: 1718104210 Timestamp [UCT]: 2024-06-11 11:10:10 Age [y:d:h:m:s]: 00:280:23:43:37
Block: 1041844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200813 RingCT/type: yes/0
Extra: 0193684a6f8a51d3d6b87ac1796c0311017da6e3798411a04f97d2b97ebc057399021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7be5d0d0514ae097baf1c06ce3d92c8a566ebb62cf65d5c1abf703ddf33020aa 0.600000000000 1510617 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": 1041854, "vin": [ { "gen": { "height": 1041844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7be5d0d0514ae097baf1c06ce3d92c8a566ebb62cf65d5c1abf703ddf33020aa" } } ], "extra": [ 1, 147, 104, 74, 111, 138, 81, 211, 214, 184, 122, 193, 121, 108, 3, 17, 1, 125, 166, 227, 121, 132, 17, 160, 79, 151, 210, 185, 126, 188, 5, 115, 153, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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