Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb2acce78b643c36b6818a43eb4b8f2b80465108f247071ee4dc7a4387e7c446

Tx prefix hash: 91775b5058ca1ef671a18ee30f9e2882f354df9dcaec4dda9f3cb6065bb19bb1
Tx public key: abf78025e5f4c7751d383666d78461faff8204fa9ab829d76378993c07823e19
Timestamp: 1748436325 Timestamp [UTC]: 2025-05-28 12:45:25 Age [y:d:h:m:s]: 00:352:20:53:34
Block: 1292775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242234 RingCT/type: yes/0
Extra: 01abf78025e5f4c7751d383666d78461faff8204fa9ab829d76378993c07823e19021100000004df096e52000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 96d4f7b7c8bc2407671e838176f4c46e6147de80839dd45da1e0a357a2780cb8 0.000600000000 1780246 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": 1292785, "vin": [ { "gen": { "height": 1292775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96d4f7b7c8bc2407671e838176f4c46e6147de80839dd45da1e0a357a2780cb8" } } ], "extra": [ 1, 171, 247, 128, 37, 229, 244, 199, 117, 29, 56, 54, 102, 215, 132, 97, 250, 255, 130, 4, 250, 154, 184, 41, 215, 99, 120, 153, 60, 7, 130, 62, 25, 2, 17, 0, 0, 0, 4, 223, 9, 110, 82, 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: