Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52ed346eb04523cf73f6d03341b7062d23736f0c85eed68bf78e9a8fdcc996cf

Tx prefix hash: 8dbe2380bfb590b2752c34ead059bf90fe0961df26b502a3da4d95db120068ce
Tx public key: 2d4182426d3fb25a37d61da68d89223fe857f0549325719e890f7bad1f4133d5
Timestamp: 1784319794 Timestamp [UTC]: 2026-07-17 20:23:14 Age [y:d:h:m:s]: 00:126:09:51:34
Block: 1583993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 99224 RingCT/type: yes/0
Extra: 012d4182426d3fb25a37d61da68d89223fe857f0549325719e890f7bad1f4133d50208f16ead17fba3eee3

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9ad0274715eab72678effa7e3cdc7cbfa5db557e55179ff85b7a43e619123254 0.000600000000 2073987 of 15 <17>

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": 1584003, "vin": [ { "gen": { "height": 1583993 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "9ad0274715eab72678effa7e3cdc7cbfa5db557e55179ff85b7a43e619123254", "view_tag": "17" } } } ], "extra": [ 1, 45, 65, 130, 66, 109, 63, 178, 90, 55, 214, 29, 166, 141, 137, 34, 63, 232, 87, 240, 84, 147, 37, 113, 158, 137, 15, 123, 173, 31, 65, 51, 213, 2, 8, 241, 110, 173, 23, 251, 163, 238, 227 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: