Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce6cfe5085b7e8bf241ca6cdb2cfa411e3470beab2bf87529247e9d6d34abfee

Tx prefix hash: dfef6552f079ce825935b6d0ec266657c4d72313f9ccc9df5504ad5b5f5daecd
Tx public key: 50e74792d3adcd3e60abc23267cf13b0e83165f885fcac2c6ef7b16366f00636
Timestamp: 1702947027 Timestamp [UCT]: 2023-12-19 00:50:27 Age [y:d:h:m:s]: 01:119:20:41:44
Block: 916177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346807 RingCT/type: yes/0
Extra: 0150e74792d3adcd3e60abc23267cf13b0e83165f885fcac2c6ef7b16366f00636021100000009faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4cda6b0a9724e585b4cd2b454e34dd9d39db06b312d050582ae888100900ba6 0.600000000000 1373659 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": 916187, "vin": [ { "gen": { "height": 916177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4cda6b0a9724e585b4cd2b454e34dd9d39db06b312d050582ae888100900ba6" } } ], "extra": [ 1, 80, 231, 71, 146, 211, 173, 205, 62, 96, 171, 194, 50, 103, 207, 19, 176, 232, 49, 101, 248, 133, 252, 172, 44, 110, 247, 177, 99, 102, 240, 6, 54, 2, 17, 0, 0, 0, 9, 250, 243, 92, 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