Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d26ea0b3a0a152892bd7561ba1ddc31059f800a8f006c990bf4ea15087e6c4a

Tx prefix hash: a396a0d8286d9495cc09097667a77e9c86f35d44c5d4fd40dd27d89c9211453a
Tx public key: 0af785cf74687670eae5c7dfd5bf45b39494e26236bb527bcaf7a0b148e40064
Timestamp: 1774427594 Timestamp [UTC]: 2026-03-25 08:33:14 Age [y:d:h:m:s]: 00:236:21:58:02
Block: 1505383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174813 RingCT/type: yes/0
Extra: 010af785cf74687670eae5c7dfd5bf45b39494e26236bb527bcaf7a0b148e40064021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2e436deb9a51d4ecfe87608117bbca8ad6fd962ad414c78c437311145f643dd1 0.000600000000 1995117 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": 1505393, "vin": [ { "gen": { "height": 1505383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e436deb9a51d4ecfe87608117bbca8ad6fd962ad414c78c437311145f643dd1" } } ], "extra": [ 1, 10, 247, 133, 207, 116, 104, 118, 112, 234, 229, 199, 223, 213, 191, 69, 179, 148, 148, 226, 98, 54, 187, 82, 123, 202, 247, 160, 177, 72, 228, 0, 100, 2, 17, 0, 0, 0, 7, 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: