Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4c247fe43ce2c77ff863f4924a306611b2f7c55ba15c02fa4fdcd739b0c68a

Tx prefix hash: 8589c8d796621020037e3844d5a9a0bddc085df4db82889ab1aa8ee1c76f7df9
Tx public key: 78b4030876a01922e437872b5e09705b1fb05b6bdd6913b697f84db3ba341cc1
Timestamp: 1764437761 Timestamp [UTC]: 2025-11-29 17:36:01 Age [y:d:h:m:s]: 00:351:00:35:21
Block: 1422848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256220 RingCT/type: yes/0
Extra: 0178b4030876a01922e437872b5e09705b1fb05b6bdd6913b697f84db3ba341cc1021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4dcbe9af2b51e36aab9c41f3a8f19397d1e120ea98e01a49d53116d738cd6903 0.000600000000 1911421 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": 1422858, "vin": [ { "gen": { "height": 1422848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dcbe9af2b51e36aab9c41f3a8f19397d1e120ea98e01a49d53116d738cd6903" } } ], "extra": [ 1, 120, 180, 3, 8, 118, 160, 25, 34, 228, 55, 135, 43, 94, 9, 112, 91, 31, 176, 91, 107, 221, 105, 19, 182, 151, 248, 77, 179, 186, 52, 28, 193, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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: