← previous blocknext block →recent activity
Analyzing
Block #93,568,083
9 transactions · 9 stateful · 2026-08-06 06:59:50 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,568,083 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x7a2c83a3…a29a
0x34b655…2a6f
4 touches
1 conflict
0xb6bb22c3…4a4f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b916121…2712
0x065c9d…c394
2 touches
0 conflicts
0xabe52feb…8f85
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0x2877f4400c…13c2c8
Audit this contract →
← previous block·next block →recent activity