Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af5fd6d68aa9c60cf94f0db76a241e788b914d013952b7d5f2c3dbe796a63d99

Tx prefix hash: 805c4ad867c4de8dc8e57ca09eddd0848fe23b46f5d65b8725d3dba975c17b58
Tx public key: d835928f9ff9ee6162b33339accf73a88b1afb96f719cef16039f89fe6a2d2db
Timestamp: 1574785039 Timestamp [UTC]: 2019-11-26 16:17:19 Age [y:d:h:m:s]: 06:359:07:22:09
Block: 18084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1663397 RingCT/type: yes/0
Extra: 01d835928f9ff9ee6162b33339accf73a88b1afb96f719cef16039f89fe6a2d2db0211000000115d286194000000000000000000

1 output(s) for total of 0.534664169211 xmr

stealth address amount amount idx tag
00: 0af35b9cf47faca72e3cce9f74351e4a5f7d452238b58930c33f8cdfa6fbf32a 0.534664169211 27068 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": 18094, "vin": [ { "gen": { "height": 18084 } } ], "vout": [ { "amount": 534664169211, "target": { "key": "0af35b9cf47faca72e3cce9f74351e4a5f7d452238b58930c33f8cdfa6fbf32a" } } ], "extra": [ 1, 216, 53, 146, 143, 159, 249, 238, 97, 98, 179, 51, 57, 172, 207, 115, 168, 139, 26, 251, 150, 247, 25, 206, 241, 96, 57, 248, 159, 230, 162, 210, 219, 2, 17, 0, 0, 0, 17, 93, 40, 97, 148, 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: