Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f6f55ff5687fa7cdec4a46a7cde1304e7970860f9a7c16891c7b2eeb0497862

Tx prefix hash: b620b07d9221c3fd1901d410fa3dca4a11f8d57d12d20c0980d90fe33cf2f71c
Tx public key: 1fffed71a3bff55ef55925104d34b44c632f977519572ab07d992f0193d38669
Timestamp: 1771759205 Timestamp [UTC]: 2026-02-22 11:20:05 Age [y:d:h:m:s]: 00:269:21:49:41
Block: 1483316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198467 RingCT/type: yes/0
Extra: 011fffed71a3bff55ef55925104d34b44c632f977519572ab07d992f0193d38669021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7e3b70d3b3c00c0518e533e7d5c18d762fef37ab86db51ac3da12545bd1c47dd 0.000600000000 1972722 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": 1483326, "vin": [ { "gen": { "height": 1483316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e3b70d3b3c00c0518e533e7d5c18d762fef37ab86db51ac3da12545bd1c47dd" } } ], "extra": [ 1, 31, 255, 237, 113, 163, 191, 245, 94, 245, 89, 37, 16, 77, 52, 180, 76, 99, 47, 151, 117, 25, 87, 42, 176, 125, 153, 47, 1, 147, 211, 134, 105, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 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: