Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c295082e9998fe0c95556a9d30684cb05afb772c727ca58f069797f2dea4ce0e

Tx prefix hash: a27ac7570ed747d7d3eb27225c1a7e158d8363eedcd03d521b1f5b20687530e7
Tx public key: af0f723a73258b0e438b8aa42f687350a0a7ba66e3e8026919077cbbc5bfaf62
Timestamp: 1574327253 Timestamp [UTC]: 2019-11-21 09:07:33 Age [y:d:h:m:s]: 06:305:10:00:49
Block: 13572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1626271 RingCT/type: yes/0
Extra: 01af0f723a73258b0e438b8aa42f687350a0a7ba66e3e8026919077cbbc5bfaf62021100000001ccefb800000000000000000000

1 output(s) for total of 0.553389884374 xmr

stealth address amount amount idx tag
00: e0831d7b30b113a614ca017fd114ff1a2b987d5b37cef2caa6fbfb96e1beb56b 0.553389884374 16223 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": 13582, "vin": [ { "gen": { "height": 13572 } } ], "vout": [ { "amount": 553389884374, "target": { "key": "e0831d7b30b113a614ca017fd114ff1a2b987d5b37cef2caa6fbfb96e1beb56b" } } ], "extra": [ 1, 175, 15, 114, 58, 115, 37, 139, 14, 67, 139, 138, 164, 47, 104, 115, 80, 160, 167, 186, 102, 227, 232, 2, 105, 25, 7, 124, 187, 197, 191, 175, 98, 2, 17, 0, 0, 0, 1, 204, 239, 184, 0, 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: