Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a96f141d7b07222fdf5b1c4923400874698dae92d1f4e0c951826e5bd44ac65

Tx prefix hash: 2d53104a3a2e4e5ad3e0982cb5ed6af879cb26d2d524ce8ef4162f55afa8a2fe
Tx public key: 122ae2a2775b1219f495e70092721f84d8e2fb26b7d3544f9374386845798e08
Timestamp: 1578317674 Timestamp [UTC]: 2020-01-06 13:34:34 Age [y:d:h:m:s]: 06:134:21:46:31
Block: 39700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1498523 RingCT/type: yes/0
Extra: 01122ae2a2775b1219f495e70092721f84d8e2fb26b7d3544f9374386845798e08021100000097b221b3d1000000000000000000

1 output(s) for total of 0.453383549952 xmr

stealth address amount amount idx tag
00: 3c60a1d80c7246ff0c9f90f778d72af8ad04a789fd7cd89aefa789f5d3d18057 0.453383549952 68860 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": 39710, "vin": [ { "gen": { "height": 39700 } } ], "vout": [ { "amount": 453383549952, "target": { "key": "3c60a1d80c7246ff0c9f90f778d72af8ad04a789fd7cd89aefa789f5d3d18057" } } ], "extra": [ 1, 18, 42, 226, 162, 119, 91, 18, 25, 244, 149, 231, 0, 146, 114, 31, 132, 216, 226, 251, 38, 183, 211, 84, 79, 147, 116, 56, 104, 69, 121, 142, 8, 2, 17, 0, 0, 0, 151, 178, 33, 179, 209, 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: