← previous blocknext block →recent activity
Analyzing
Block #93,556,341
8 transactions · 7 stateful · 2026-08-06 06:00:48 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,556,341 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02c03ee2…3de5
0x34b655…2a6f
4 touches
1 conflict
0x7a2c83a3…a29a
0x34b655…2a6f
4 touches
1 conflict
0x8218911e…3bed
0x34b655…2a6f
4 touches
1 conflict
0x03083ef6…08aa
0x34b655…2a6f
2 touches
0 conflicts
0x0dfbb457…baaf
0x34b655…2a6f
2 touches
0 conflicts
0x157536c0…33ef
0x34b655…2a6f
2 touches
0 conflicts
0x16abeb93…7801
0x34b655…2a6f
2 touches
0 conflicts
0x2cbead00…5def
0x34b655…2a6f
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
1 conflict on slot 0x02c03ee228…b43de5
Audit this contract →
← previous block·next block →recent activity