← previous blocknext block →recent activity
Analyzing
Block #93,400,873
21 transactions · 18 stateful · 2026-08-05 16:59:14 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,400,873 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w110w311w113w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
4 touches
1 conflict
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0x8fe37a3f…4c89
0x34b655…2a6f
4 touches
1 conflict
0xa1bdd5c6…fbd1
0x34b655…2a6f
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity