Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a99606cf7f4ba21586451ae7f617556089e875381e6845cfa4bb8122a42bd05

Tx prefix hash: c4e72a8774303e60cfe98df1575fff0850c26b1b123e4a52a5dfea8216dfd5aa
Tx public key: d10bce4388e652c74ee2aef61e019e9dec34794de820e8bbb9cbb9a8c4772dee
Timestamp: 1695812478 Timestamp [UCT]: 2023-09-27 11:01:18 Age [y:d:h:m:s]: 01:204:07:43:00
Block: 857235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407093 RingCT/type: yes/0
Extra: 01d10bce4388e652c74ee2aef61e019e9dec34794de820e8bbb9cbb9a8c4772dee02110000000533af99f4000000000000000000

1 output(s) for total of 0.886389567000 dcy

stealth address amount amount idx
00: 4bb88c8710c1c1c6f00162e429f62fb81763b96b9e5c8aa6cd411f7be7408d3d 0.886389567000 1311347 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": 857245, "vin": [ { "gen": { "height": 857235 } } ], "vout": [ { "amount": 886389567, "target": { "key": "4bb88c8710c1c1c6f00162e429f62fb81763b96b9e5c8aa6cd411f7be7408d3d" } } ], "extra": [ 1, 209, 11, 206, 67, 136, 230, 82, 199, 78, 226, 174, 246, 30, 1, 158, 157, 236, 52, 121, 77, 232, 32, 232, 187, 185, 203, 185, 168, 196, 119, 45, 238, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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