Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21bffec8baf9523a7fe9b41f789e0d8e60267fae3ff2b166f819d57fb24eed3b

Tx prefix hash: ffe5d5f1049a2d796aebacadb94e0cd113b75053cbd4306175dffc36e7f820b6
Tx public key: 0c3a0bd69f42bc4f2325bdb75cacb3c3277d6baf5c87a9d3ad586527e7608642
Timestamp: 1663409955 Timestamp [UTC]: 2022-09-17 10:19:15 Age [y:d:h:m:s]: 03:243:05:01:46
Block: 589823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 946146 RingCT/type: yes/0
Extra: 010c3a0bd69f42bc4f2325bdb75cacb3c3277d6baf5c87a9d3ad586527e7608642021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.006818229706 xmr

stealth address amount amount idx tag
00: c41f487c975d8e7b89dad9a27a7ff907d286ec6ff9173adb3312443bc819343c 0.006818229706 1024170 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": 589833, "vin": [ { "gen": { "height": 589823 } } ], "vout": [ { "amount": 6818229706, "target": { "key": "c41f487c975d8e7b89dad9a27a7ff907d286ec6ff9173adb3312443bc819343c" } } ], "extra": [ 1, 12, 58, 11, 214, 159, 66, 188, 79, 35, 37, 189, 183, 92, 172, 179, 195, 39, 125, 107, 175, 92, 135, 169, 211, 173, 88, 101, 39, 231, 96, 134, 66, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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: