Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1430f7dfd9225cfd1cf6834e628dde9392565adeee366e536f5e45cf19ef570

Tx prefix hash: e6ca478069b52c155eda0900f5e7bda4e654f95550a5d48148493afd15e69985
Tx public key: 2ebee377c5ae0004ce53f8ea793f640d0515f21ffdbd9429395236d7aa772d1f
Timestamp: 1772030939 Timestamp [UTC]: 2026-02-25 14:48:59 Age [y:d:h:m:s]: 00:267:21:14:40
Block: 1485597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197076 RingCT/type: yes/0
Extra: 012ebee377c5ae0004ce53f8ea793f640d0515f21ffdbd9429395236d7aa772d1f021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: adf47825fb8f320b2dde3fafeef36b1219ae08f489b671f95f20d9a16c1647d8 0.000600000000 1975035 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": 1485607, "vin": [ { "gen": { "height": 1485597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adf47825fb8f320b2dde3fafeef36b1219ae08f489b671f95f20d9a16c1647d8" } } ], "extra": [ 1, 46, 190, 227, 119, 197, 174, 0, 4, 206, 83, 248, 234, 121, 63, 100, 13, 5, 21, 242, 31, 253, 189, 148, 41, 57, 82, 54, 215, 170, 119, 45, 31, 2, 17, 0, 0, 0, 4, 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: