Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5bbd98fabbd2b0d4da76ec58ba651e900a7b6cb973d332f5dd80bc72ab0e77

Tx prefix hash: f627feab18fbe70a00bb2929d947bd0584336176176e0b05d594ef4a4f3f83c3
Tx public key: d9bf55f2bd98163dd5091237327e37aee965e0936bec05ccad8742ba4de2fdbe
Timestamp: 1773960360 Timestamp [UTC]: 2026-03-19 22:46:00 Age [y:d:h:m:s]: 00:240:07:25:22
Block: 1501507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177184 RingCT/type: yes/0
Extra: 01d9bf55f2bd98163dd5091237327e37aee965e0936bec05ccad8742ba4de2fdbe021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f6db36bee1a1cace415ba69e147c2f0f46a83883b74f305aae6a0a2ed88675a3 0.000600000000 1991191 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": 1501517, "vin": [ { "gen": { "height": 1501507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6db36bee1a1cace415ba69e147c2f0f46a83883b74f305aae6a0a2ed88675a3" } } ], "extra": [ 1, 217, 191, 85, 242, 189, 152, 22, 61, 213, 9, 18, 55, 50, 126, 55, 174, 233, 101, 224, 147, 107, 236, 5, 204, 173, 135, 66, 186, 77, 226, 253, 190, 2, 17, 0, 0, 0, 3, 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: