Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0038d3f6c9ed0857f0cbcd07e058d1ed0f80783edbbf5c0ef3e25b8e0067fbe6

Tx prefix hash: b52322c96b23553b3c923346d240e43df2cbcf961d2d04d5458e84e3544c1228
Tx public key: 1a92c2261e49e32bff93c81dcfc4f9bcb5b63b57bb6eaf4b8a51542d74ea330d
Timestamp: 1755667791 Timestamp [UTC]: 2025-08-20 05:29:51 Age [y:d:h:m:s]: 01:091:19:41:38
Block: 1350368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331924 RingCT/type: yes/0
Extra: 011a92c2261e49e32bff93c81dcfc4f9bcb5b63b57bb6eaf4b8a51542d74ea330d021100000008b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f7580566e5027c0225a7766317a3d3563f0dbff181252899580c22f4c23ff07 0.000600000000 1838313 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": 1350378, "vin": [ { "gen": { "height": 1350368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f7580566e5027c0225a7766317a3d3563f0dbff181252899580c22f4c23ff07" } } ], "extra": [ 1, 26, 146, 194, 38, 30, 73, 227, 43, 255, 147, 200, 29, 207, 196, 249, 188, 181, 182, 59, 87, 187, 110, 175, 75, 138, 81, 84, 45, 116, 234, 51, 13, 2, 17, 0, 0, 0, 8, 178, 247, 132, 196, 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: