Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd8350c77d9e17ee09d56deae14a20bad520e835e49db77eb7792f7083da613

Tx prefix hash: 59bf05530761cdd1ae0461b130b83050239a8abcbe7584cb924a905b80550e10
Tx public key: 535a3850d4fef6ad0a9ab64d201f824fede9f83d4f00cfff2f0958fe908c3b74
Timestamp: 1772374423 Timestamp [UTC]: 2026-03-01 14:13:43 Age [y:d:h:m:s]: 00:265:07:59:35
Block: 1488400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195094 RingCT/type: yes/0
Extra: 01535a3850d4fef6ad0a9ab64d201f824fede9f83d4f00cfff2f0958fe908c3b74021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd4064d946a3a82f954eb0f09e669aa325d14bb4074f33e693c6c44a5b8e5ffb 0.000600000000 1977878 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": 1488410, "vin": [ { "gen": { "height": 1488400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd4064d946a3a82f954eb0f09e669aa325d14bb4074f33e693c6c44a5b8e5ffb" } } ], "extra": [ 1, 83, 90, 56, 80, 212, 254, 246, 173, 10, 154, 182, 77, 32, 31, 130, 79, 237, 233, 248, 61, 79, 0, 207, 255, 47, 9, 88, 254, 144, 140, 59, 116, 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: