Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e3a285fd641f6b4eacc8ef127a26c1cc044f644ec824a568e0b1d79e063ec1

Tx prefix hash: 29b078ea50652960771ad570cc34de3485de242be4e39536d521b158d9d56ac4
Tx public key: 86fa37164c278614be7fe2e945151961ec6836dfb3848e06c37b3f8c9b25e65d
Timestamp: 1582533874 Timestamp [UCT]: 2020-02-24 08:44:34 Age [y:d:h:m:s]: 04:266:04:26:40
Block: 71629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1082633 RingCT/type: yes/0
Extra: 0186fa37164c278614be7fe2e945151961ec6836dfb3848e06c37b3f8c9b25e65d02110000000d8a2ee0d9000000000000000000

1 output(s) for total of 355.356439398000 dcy

stealth address amount amount idx
00: 65368b048ccddc1219325ba9cfb294abc14d9ab7884bc322aee781abccf86be3 355.356439398000 132290 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": 71639, "vin": [ { "gen": { "height": 71629 } } ], "vout": [ { "amount": 355356439398, "target": { "key": "65368b048ccddc1219325ba9cfb294abc14d9ab7884bc322aee781abccf86be3" } } ], "extra": [ 1, 134, 250, 55, 22, 76, 39, 134, 20, 190, 127, 226, 233, 69, 21, 25, 97, 236, 104, 54, 223, 179, 132, 142, 6, 195, 123, 63, 140, 155, 37, 230, 93, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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