Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82f4bcb0522a694f967fbefce282f675af7e3a5a9d1feae00f99c826e3bf08c8

Tx prefix hash: 1f7c0d3ad2a63b3e27bf09e26119e23ebdf44bf14f6bc06cd6e84b0d1c5f26e3
Tx public key: 0fab38d865383db36304188e92fa49899b01f99ed2abd5d1a5851195cc9d3a73
Timestamp: 1795129441 Timestamp [UTC]: 2026-11-19 23:04:01 Age [y:d:h:m:s]: 00:002:17:59:15
Block: 1682226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 1268 RingCT/type: yes/0
Extra: 010fab38d865383db36304188e92fa49899b01f99ed2abd5d1a5851195cc9d3a73

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fa3d4242ee49e11459fd25ed607a281dec34ff2e53f9e7ef8d46f7ae10facfd9 0.000600000000 2173036 of 15 <d0>

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": 1682236, "vin": [ { "gen": { "height": 1682226 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "fa3d4242ee49e11459fd25ed607a281dec34ff2e53f9e7ef8d46f7ae10facfd9", "view_tag": "d0" } } } ], "extra": [ 1, 15, 171, 56, 216, 101, 56, 61, 179, 99, 4, 24, 142, 146, 250, 73, 137, 155, 1, 249, 158, 210, 171, 213, 209, 165, 133, 17, 149, 204, 157, 58, 115 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: