Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d057a2ee5fe889643039d21f985ffca0e528cb24bd30df91e2c82864975eeb7

Tx prefix hash: 5f2077e9d1e16292dad31c1a45fc74812e9e36a88f9b0bd84639aa15d6a016a9
Tx public key: 5c46f816f25b7a772991cd7d5504c2ca6f01064922e965b66409c2bff71771ce
Timestamp: 1593017910 Timestamp [UCT]: 2020-06-24 16:58:30 Age [y:d:h:m:s]: 04:188:09:36:43
Block: 110494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074941 RingCT/type: yes/0
Extra: 015c46f816f25b7a772991cd7d5504c2ca6f01064922e965b66409c2bff71771ce02110000002246a11e8a000000000000000000

1 output(s) for total of 264.172895938000 dcy

stealth address amount amount idx
00: 0f3725aee35c0648353239436d297b7fecccef84225a2464d3942cb3ebbecfe9 264.172895938000 191380 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": 110504, "vin": [ { "gen": { "height": 110494 } } ], "vout": [ { "amount": 264172895938, "target": { "key": "0f3725aee35c0648353239436d297b7fecccef84225a2464d3942cb3ebbecfe9" } } ], "extra": [ 1, 92, 70, 248, 22, 242, 91, 122, 119, 41, 145, 205, 125, 85, 4, 194, 202, 111, 1, 6, 73, 34, 233, 101, 182, 100, 9, 194, 191, 247, 23, 113, 206, 2, 17, 0, 0, 0, 34, 70, 161, 30, 138, 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