Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fb3def230a9231e7f2f19eeafce9a84eab68c380aa0c50f28be0f7aa13b3193

Tx prefix hash: 0eeebdd0c559a094e3879d551da4042139bac83421150265bdfa5278cf8a4fc0
Tx public key: 3db37228782a365890a4469dc2e73de3119673d1c78ac47b82aa33d8257501b5
Timestamp: 1748152712 Timestamp [UTC]: 2025-05-25 05:58:32 Age [y:d:h:m:s]: 00:357:16:37:12
Block: 1290420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245783 RingCT/type: yes/0
Extra: 013db37228782a365890a4469dc2e73de3119673d1c78ac47b82aa33d8257501b5021100000003a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2d80ace931a55f5af5c580c098055fb8a3f847d21fcbe2b24347bfafeaccc620 0.000600000000 1777889 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": 1290430, "vin": [ { "gen": { "height": 1290420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d80ace931a55f5af5c580c098055fb8a3f847d21fcbe2b24347bfafeaccc620" } } ], "extra": [ 1, 61, 179, 114, 40, 120, 42, 54, 88, 144, 164, 70, 157, 194, 231, 61, 227, 17, 150, 115, 209, 199, 138, 196, 123, 130, 170, 51, 216, 37, 117, 1, 181, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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: