← previous blocknext block →recent activity
Analyzing
Block #93,313,631
17 transactions · 17 stateful · 2026-08-05 09:40:36 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,313,631 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w27w38w49w110w511w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x463017a2…d628
0x851145…3f07
6 touches
3 conflicts
0x89935301…af69
0x34b655…2a6f
4 touches
1 conflict
0x8eead23a…46e8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
6 conflicts on slot 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity