Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22983edc03d9f89e091766d70a798f38e5496f528e68e9b45c227e2a62fcce91

Tx prefix hash: e9519b9df625dd53b95b18032062a7f48e2e604cbcf2a2bfcf87868795f5eaf0
Tx public key: 18a0ecc660549be23a34ecda028c15dc5aa791d414bdec1cb519a0449b621489
Timestamp: 1579897480 Timestamp [UTC]: 2020-01-24 20:24:40 Age [y:d:h:m:s]: 06:301:06:55:44
Block: 52231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1630127 RingCT/type: yes/0
Extra: 0118a0ecc660549be23a34ecda028c15dc5aa791d414bdec1cb519a0449b621489021100000015d81c26c0000000000000000000

1 output(s) for total of 0.412071854699 xmr

stealth address amount amount idx tag
00: 7d200180466fe9d08adc9cdc077135a771bfa7302e47a8dddc1caca64f46dc13 0.412071854699 96770 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 dinastycoin-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": 52241, "vin": [ { "gen": { "height": 52231 } } ], "vout": [ { "amount": 412071854699, "target": { "key": "7d200180466fe9d08adc9cdc077135a771bfa7302e47a8dddc1caca64f46dc13" } } ], "extra": [ 1, 24, 160, 236, 198, 96, 84, 155, 226, 58, 52, 236, 218, 2, 140, 21, 220, 90, 167, 145, 212, 20, 189, 236, 28, 181, 25, 160, 68, 155, 98, 20, 137, 2, 17, 0, 0, 0, 21, 216, 28, 38, 192, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: