Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddda7b60ee22bb87bd8d9657173228bcaedcb84e5cee284321dfd7d3561a5651

Tx prefix hash: a098867d918c25b276cd46534b75e3cb68525115e990e66749e6e8a8b922f75f
Tx public key: 38773e5c83358bb67c4a26f18e8d9709e5de1c7fec783db40712237f9e6c9a25
Timestamp: 1774604627 Timestamp [UTC]: 2026-03-27 09:43:47 Age [y:d:h:m:s]: 00:233:09:31:17
Block: 1506844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172261 RingCT/type: yes/0
Extra: 0138773e5c83358bb67c4a26f18e8d9709e5de1c7fec783db40712237f9e6c9a25021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 973550ff8f02051599758ae1fd69a925208c37bf0cba7b4b8b957f15b3c777b8 0.000600000000 1996592 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": 1506854, "vin": [ { "gen": { "height": 1506844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "973550ff8f02051599758ae1fd69a925208c37bf0cba7b4b8b957f15b3c777b8" } } ], "extra": [ 1, 56, 119, 62, 92, 131, 53, 139, 182, 124, 74, 38, 241, 142, 141, 151, 9, 229, 222, 28, 127, 236, 120, 61, 180, 7, 18, 35, 127, 158, 108, 154, 37, 2, 17, 0, 0, 0, 2, 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: