← previous blocknext block →recent activity
Analyzing
Block #93,592,932
13 transactions · 13 stateful · 2026-08-06 09:04:44 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,592,932 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w39w411w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb44cedd…c666
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x646278ac…2ebf
0x34b655…2a6f
4 touches
1 conflict
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0x71e1dee6…d11b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
3 conflicts on slot 0xbb44cedda5…77c666
Audit this contract →
← previous block·next block →recent activity