Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc7ea4925214bb47dddb92078d2224fdc3a5a02bdc4860e367a3acdeb61405e9

Tx prefix hash: c82edc04ddb6324b077050145d99cf2cb7dac4f9b17c24ce379bc71e332d2767
Tx public key: 557ca31ecba9fc8af23c707e78b368dfea67eb53eb229881e92d6d922389eb8e
Timestamp: 1743831132 Timestamp [UTC]: 2025-04-05 05:32:12 Age [y:d:h:m:s]: 01:226:03:01:04
Block: 1254630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425634 RingCT/type: yes/0
Extra: 01557ca31ecba9fc8af23c707e78b368dfea67eb53eb229881e92d6d922389eb8e0211000000044060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 93ac099000873f4c580f27590f51cca5d679043ed1eb3a760a0d50ef4d31ec3b 0.000600000000 1741711 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": 1254640, "vin": [ { "gen": { "height": 1254630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93ac099000873f4c580f27590f51cca5d679043ed1eb3a760a0d50ef4d31ec3b" } } ], "extra": [ 1, 85, 124, 163, 30, 203, 169, 252, 138, 242, 60, 112, 126, 120, 179, 104, 223, 234, 103, 235, 83, 235, 34, 152, 129, 233, 45, 109, 146, 35, 137, 235, 142, 2, 17, 0, 0, 0, 4, 64, 96, 246, 210, 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: