Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e32e47ca444e5fee6638c068bd7e03f0c792327e7a093b58f99099482d5fe4c7

Tx prefix hash: 3b16bc465852c523704c39951e5a1284531b5c4a2d33ad4f62c478aecc5396e8
Tx public key: a0082f774ac3a6d8f726f8aaef009f828c9c38a340882488c881fa014f1dd942
Timestamp: 1577761488 Timestamp [UCT]: 2019-12-31 03:04:48 Age [y:d:h:m:s]: 05:005:21:16:03
Block: 35435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154229 RingCT/type: yes/0
Extra: 01a0082f774ac3a6d8f726f8aaef009f828c9c38a340882488c881fa014f1dd942021100000012d81c26c0000000000000000000

1 output(s) for total of 468.370991819000 dcy

stealth address amount amount idx
00: 325aef11255c64e7d09bfca22a3433743bb428c2aecfe3cc940532459dccdea7 468.370991819000 59760 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": 35445, "vin": [ { "gen": { "height": 35435 } } ], "vout": [ { "amount": 468370991819, "target": { "key": "325aef11255c64e7d09bfca22a3433743bb428c2aecfe3cc940532459dccdea7" } } ], "extra": [ 1, 160, 8, 47, 119, 74, 195, 166, 216, 247, 38, 248, 170, 239, 0, 159, 130, 140, 156, 56, 163, 64, 136, 36, 136, 200, 129, 250, 1, 79, 29, 217, 66, 2, 17, 0, 0, 0, 18, 216, 28, 38, 192, 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