Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e776df63dbf9a87e284382f194f2f99e73738eba543443928acca63fb4d6a8f

Tx prefix hash: 446c506314b52577f75f951a469a53b501d4326c0feeb6724edb301ea0c7079c
Tx public key: 87bf4dd1435dc9b1165d8c03b365a13ee0ce99c6f0255675add6d2812b84d09d
Timestamp: 1733445195 Timestamp [UCT]: 2024-12-06 00:33:15 Age [y:d:h:m:s]: 00:106:07:52:15
Block: 1168913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75796 RingCT/type: yes/0
Extra: 0187bf4dd1435dc9b1165d8c03b365a13ee0ce99c6f0255675add6d2812b84d09d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb72bb2968b956ea906a113566a79d8dbb7918331a4638f5991d54db45dc8078 0.600000000000 1654626 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": 1168923, "vin": [ { "gen": { "height": 1168913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb72bb2968b956ea906a113566a79d8dbb7918331a4638f5991d54db45dc8078" } } ], "extra": [ 1, 135, 191, 77, 209, 67, 93, 201, 177, 22, 93, 140, 3, 179, 101, 161, 62, 224, 206, 153, 198, 240, 37, 86, 117, 173, 214, 210, 129, 43, 132, 208, 157, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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