Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4fb4e3072a36e7dda2fd29dbb1558049bc13b9b753117693912f09cfef5456d

Tx prefix hash: cbe75d5fd77ec28d502c73f0bee7b7e5be9a851172c7672b2f727932a9def775
Tx public key: fe63ecca5635d6405e49d148c749909530a2a3ff70e8f3937f99526938674404
Timestamp: 1760825904 Timestamp [UTC]: 2025-10-18 22:18:24 Age [y:d:h:m:s]: 01:029:14:48:03
Block: 1392920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287473 RingCT/type: yes/0
Extra: 01fe63ecca5635d6405e49d148c749909530a2a3ff70e8f3937f9952693867440402110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a1371adc147969022ea5097b9f9a24f74cd5a2fa7f5ff8a5ba7037a0e2c49799 0.000600000000 1881177 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": 1392930, "vin": [ { "gen": { "height": 1392920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1371adc147969022ea5097b9f9a24f74cd5a2fa7f5ff8a5ba7037a0e2c49799" } } ], "extra": [ 1, 254, 99, 236, 202, 86, 53, 214, 64, 94, 73, 209, 72, 199, 73, 144, 149, 48, 162, 163, 255, 112, 232, 243, 147, 127, 153, 82, 105, 56, 103, 68, 4, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: