Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e414a8e1665befe022abb0e35b75b530aa6f8127b0bd18bb7ae3ef479f97f9df

Tx prefix hash: e7d123266f31e78618a33d64392c7e525aeac44cb93b9af3cda88f44912c502b
Tx public key: 1acae2cec7b26bb42e570996139e08e8ee0af3729d8554e01caab48534dd1042
Timestamp: 1578440270 Timestamp [UCT]: 2020-01-07 23:37:50 Age [y:d:h:m:s]: 04:323:23:03:59
Block: 40854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120854 RingCT/type: yes/0
Extra: 011acae2cec7b26bb42e570996139e08e8ee0af3729d8554e01caab48534dd104202110000001a49b77a3d000000000000000000

1 output(s) for total of 449.411319764000 dcy

stealth address amount amount idx
00: 81531ae25ecb3ae5136f22ff1b5f5e4385c577164688305189aa1d40a5c96faf 449.411319764000 72179 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": 40864, "vin": [ { "gen": { "height": 40854 } } ], "vout": [ { "amount": 449411319764, "target": { "key": "81531ae25ecb3ae5136f22ff1b5f5e4385c577164688305189aa1d40a5c96faf" } } ], "extra": [ 1, 26, 202, 226, 206, 199, 178, 107, 180, 46, 87, 9, 150, 19, 158, 8, 232, 238, 10, 243, 114, 157, 133, 84, 224, 28, 170, 180, 133, 52, 221, 16, 66, 2, 17, 0, 0, 0, 26, 73, 183, 122, 61, 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