Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f4b53cc1564db87fb70309f47dd6d0cd82277e5f0a01f9abb4857bd7da2f0da

Tx prefix hash: 8ea3c4a97f6f0b5d288b91855e00499cb695ca3d6c41c07559e906ee6ab7f37b
Tx public key: 20263d93210b0216b0bb8e11bcfb38d28cb4d54c1823aea8bb26983b82e4c8aa
Timestamp: 1773163358 Timestamp [UTC]: 2026-03-10 17:22:38 Age [y:d:h:m:s]: 00:247:21:30:44
Block: 1494923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182540 RingCT/type: yes/0
Extra: 0120263d93210b0216b0bb8e11bcfb38d28cb4d54c1823aea8bb26983b82e4c8aa021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 55abebf0b162dcfa1deb68e3ec5be7559dce94faa4abb38aec86f97be56b2251 0.000600000000 1984505 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": 1494933, "vin": [ { "gen": { "height": 1494923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55abebf0b162dcfa1deb68e3ec5be7559dce94faa4abb38aec86f97be56b2251" } } ], "extra": [ 1, 32, 38, 61, 147, 33, 11, 2, 22, 176, 187, 142, 17, 188, 251, 56, 210, 140, 180, 213, 76, 24, 35, 174, 168, 187, 38, 152, 59, 130, 228, 200, 170, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: