← previous blocknext block →recent activity
Analyzing
Block #93,444,079
33 transactions · 30 stateful · 2026-08-05 20:36:27 UTC
Parallelism
94/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,444,079 · 33 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
3w04w115w016w017w118w125w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x9feedc78…da4a
0x754704…b603
2 touches
0 conflicts
0xcf3f3349…b858
0x754704…b603
2 touches
0 conflicts
0xe96cbc90…be66
0x754704…b603
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 0x91b0f8edc5…b76bd6
Audit this contract →
← previous block·next block →recent activity