← previous blocknext block →recent activity
Analyzing
Block #93,176,793
11 transactions · 10 stateful · 2026-08-04 22:12:37 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,176,793 · 11 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
2w03w14w27w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e22f39d…b92b
0x34b655…2a6f
6 touches
3 conflicts
0xe8495ea8…10e6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xfe449cf3…289f
0x34b655…2a6f
4 touches
1 conflict
0x43076802…d920
0x34b655…2a6f
4 touches
1 conflict
0x5e2b6bf6…0b3d
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
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 0x0e22f39dda…aab92b
Audit this contract →
← previous block·next block →recent activity