Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4eded28507c712891e86139d2013db7d498fc22ce7a61abbcc9ac414c72fa28c

Tx prefix hash: 8dddd1de04e86781ba271fa928d5ebc9eb64117a7b7a9ba1c61c62317202f2ae
Tx public key: d14694540bc636840b255d173eaa30a8fc6362d81b41379d28e565c5a98a11f3
Timestamp: 1765717014 Timestamp [UTC]: 2025-12-14 12:56:54 Age [y:d:h:m:s]: 00:339:04:23:39
Block: 1433428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247845 RingCT/type: yes/0
Extra: 01d14694540bc636840b255d173eaa30a8fc6362d81b41379d28e565c5a98a11f3021100000004defb8f18000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2e007021701f9bfdbb6910f4f18065c0aba6ad602c4b4434f78f0987b9c11b51 0.000600000000 1922207 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": 1433438, "vin": [ { "gen": { "height": 1433428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e007021701f9bfdbb6910f4f18065c0aba6ad602c4b4434f78f0987b9c11b51" } } ], "extra": [ 1, 209, 70, 148, 84, 11, 198, 54, 132, 11, 37, 93, 23, 62, 170, 48, 168, 252, 99, 98, 216, 27, 65, 55, 157, 40, 229, 101, 197, 169, 138, 17, 243, 2, 17, 0, 0, 0, 4, 222, 251, 143, 24, 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: