← previous blocknext block →recent activity
Analyzing
Block #93,232,128
10 transactions · 9 stateful · 2026-08-05 02:50:49 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,232,128 · 10 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
2w03w16w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3550075a…fb0f
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc9eaa844…2344
0x34b655…2a6f
4 touches
1 conflict
0x2a985122…ca00
0xd32edf…ff58
3 touches
1 conflict
0x38332f14…daf7
0x065c9d…c394
2 touches
0 conflicts
0x501b3004…5e4f
0x065c9d…c394
2 touches
0 conflicts
0xc9e2adb0…90d5
0x065c9d…c394
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 0x3550075a11…dafb0f
Audit this contract →
← previous block·next block →recent activity