Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64aaec2d12c0bbc831f81971a9f04872d69240fdd45afe31fdec85e65e981d96

Tx prefix hash: b758e8ad80a964fc7f8160282af3371de538f0717f2c9beacb47ffb33ac83f92
Tx public key: ffb76bd6e9d20e811365134b2aa9328124afa277824f50f5ca2ef429b6edb68e
Timestamp: 1743349604 Timestamp [UTC]: 2025-03-30 15:46:44 Age [y:d:h:m:s]: 01:227:11:54:39
Block: 1250636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426477 RingCT/type: yes/0
Extra: 01ffb76bd6e9d20e811365134b2aa9328124afa277824f50f5ca2ef429b6edb68e0211000000021a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a0fac462380cb16597af666a99e7e4bf8dd7334b5774aaf05d12d36524b21b3 0.000600000000 1737687 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": 1250646, "vin": [ { "gen": { "height": 1250636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a0fac462380cb16597af666a99e7e4bf8dd7334b5774aaf05d12d36524b21b3" } } ], "extra": [ 1, 255, 183, 107, 214, 233, 210, 14, 129, 19, 101, 19, 75, 42, 169, 50, 129, 36, 175, 162, 119, 130, 79, 80, 245, 202, 46, 244, 41, 182, 237, 182, 142, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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: