Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7f7eab1048db723566bb9e47c8ce2a9c1e2696174c40d66ca6f577b3b9a64a0

Tx prefix hash: b6471fc725c8a839d33d44a5bb9a7d17c6ea397f165a9395fad1c0c2215a063b
Tx public key: bb8b6f98f2fca77816152f6c58ae69a438b21abe8308b176f8037431bae7ce9b
Timestamp: 1773175836 Timestamp [UTC]: 2026-03-10 20:50:36 Age [y:d:h:m:s]: 00:251:23:27:09
Block: 1495031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185582 RingCT/type: yes/0
Extra: 01bb8b6f98f2fca77816152f6c58ae69a438b21abe8308b176f8037431bae7ce9b021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5b4d98ea12c0a301b2da88460d74c268ab8e72a6d8cae0423f28b294687b6f80 0.000600000000 1984639 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": 1495041, "vin": [ { "gen": { "height": 1495031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b4d98ea12c0a301b2da88460d74c268ab8e72a6d8cae0423f28b294687b6f80" } } ], "extra": [ 1, 187, 139, 111, 152, 242, 252, 167, 120, 22, 21, 47, 108, 88, 174, 105, 164, 56, 178, 26, 190, 131, 8, 177, 118, 248, 3, 116, 49, 186, 231, 206, 155, 2, 17, 0, 0, 0, 2, 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: