Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3e5ddb2a35f4432553c1f157d5ec37f0a8891b5e46d01d9dcee17a9c49d70b1

Tx prefix hash: 2663f2121713b4236fc78812d11946e286824c16070739fe78be96c634ba9ac4
Tx public key: bf3a41c73139fe9a4e0b13389e70c9da2835135879dcb28ab2ba1ca29395a0e8
Timestamp: 1682617327 Timestamp [UCT]: 2023-04-27 17:42:07 Age [y:d:h:m:s]: 01:203:11:16:18
Block: 747879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406871 RingCT/type: yes/0
Extra: 01bf3a41c73139fe9a4e0b13389e70c9da2835135879dcb28ab2ba1ca29395a0e80211000000037e406890000000000000000000

1 output(s) for total of 2.041581022000 dcy

stealth address amount amount idx
00: 2bab2ebfdfec96fd8aa241c3aa03f39a4e668f696e111f9a5144d6f0c4edb1bb 2.041581022000 1195644 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": 747889, "vin": [ { "gen": { "height": 747879 } } ], "vout": [ { "amount": 2041581022, "target": { "key": "2bab2ebfdfec96fd8aa241c3aa03f39a4e668f696e111f9a5144d6f0c4edb1bb" } } ], "extra": [ 1, 191, 58, 65, 199, 49, 57, 254, 154, 78, 11, 19, 56, 158, 112, 201, 218, 40, 53, 19, 88, 121, 220, 178, 138, 178, 186, 28, 162, 147, 149, 160, 232, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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