Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae384d61b232a3dbfb94db3f5c3b828a130cf782670d495c01f1150978e32295

Tx prefix hash: b9a96bb83ef897db63258d92c42f337c9aeb8d606839cd9613e5a58a2f60eb0a
Tx public key: b56a7282015cc4eb4c6fec8da5d6feef2d7ce565b18f807cd2b203c9aa0fef60
Timestamp: 1726919223 Timestamp [UCT]: 2024-09-21 11:47:03 Age [y:d:h:m:s]: 01:017:08:37:16
Block: 1114920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270759 RingCT/type: yes/0
Extra: 01b56a7282015cc4eb4c6fec8da5d6feef2d7ce565b18f807cd2b203c9aa0fef6002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 240488df0637c48c9fd476d4eb7cc723eed6041411a226e498d6a588b7f943ca 0.600000000000 1594867 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": 1114930, "vin": [ { "gen": { "height": 1114920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "240488df0637c48c9fd476d4eb7cc723eed6041411a226e498d6a588b7f943ca" } } ], "extra": [ 1, 181, 106, 114, 130, 1, 92, 196, 235, 76, 111, 236, 141, 165, 214, 254, 239, 45, 124, 229, 101, 177, 143, 128, 124, 210, 178, 3, 201, 170, 15, 239, 96, 2, 17, 0, 0, 0, 2, 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