Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d584ebefa2db91c7c71125aa9d7911217ce73d84b9507ddcb9268a1d108ecb55

Tx prefix hash: b9c2cccda5f98ebf1797ca2a2be569621097b239429597ae0d264e62035cb8ca
Tx public key: 36a540fae62403e502a269591d8377d3cb045f503dfbeee33b644859e2aa3c0b
Timestamp: 1771750262 Timestamp [UTC]: 2026-02-22 08:51:02 Age [y:d:h:m:s]: 00:269:22:47:21
Block: 1483238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198491 RingCT/type: yes/0
Extra: 0136a540fae62403e502a269591d8377d3cb045f503dfbeee33b644859e2aa3c0b021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d6e097ff9447b9f516a7c96027545f3c63aacb9ef243bd28b4d3e20fde3a9bd6 0.000600000000 1972642 of 15 -

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": 1483248, "vin": [ { "gen": { "height": 1483238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6e097ff9447b9f516a7c96027545f3c63aacb9ef243bd28b4d3e20fde3a9bd6" } } ], "extra": [ 1, 54, 165, 64, 250, 230, 36, 3, 229, 2, 162, 105, 89, 29, 131, 119, 211, 203, 4, 95, 80, 61, 251, 238, 227, 59, 100, 72, 89, 226, 170, 60, 11, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: