Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddbbcb6da65004f8c44706e7d5640a7120e174b2264254d2c5ca4f7e00ce92bc

Tx prefix hash: 28c7919130a0d5997f1fae2a0cd46bf5fcfb65d1ed891b58f8fc90b855d6526e
Tx public key: 173f06dcb66d39a82047fae93802ef4cfc1518c87636f55e4594f9e7faec934c
Timestamp: 1656965820 Timestamp [UTC]: 2022-07-04 20:17:00 Age [y:d:h:m:s]: 04:138:03:18:22
Block: 536676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1144803 RingCT/type: yes/0
Extra: 01173f06dcb66d39a82047fae93802ef4cfc1518c87636f55e4594f9e7faec934c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.010227506849 xmr

stealth address amount amount idx tag
00: 38d1282596bf19e0b45764e0cfb0459767f6705a2eeece6e4006e23c315c5539 0.010227506849 966463 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": 536686, "vin": [ { "gen": { "height": 536676 } } ], "vout": [ { "amount": 10227506849, "target": { "key": "38d1282596bf19e0b45764e0cfb0459767f6705a2eeece6e4006e23c315c5539" } } ], "extra": [ 1, 23, 63, 6, 220, 182, 109, 57, 168, 32, 71, 250, 233, 56, 2, 239, 76, 252, 21, 24, 200, 118, 54, 245, 94, 69, 148, 249, 231, 250, 236, 147, 76, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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: