← previous blocknext block →recent activity
Analyzing
Block #92,008,341
12 transactions · 11 stateful · 2026-07-31 20:12:52 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,008,341 · 12 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
1w03w14w06w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427c9fc4…5cee
0x34b655…2a6f
4 touches
1 conflict
0x1eb410fd…591d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbffde283…3385
0x34b655…2a6f
4 touches
1 conflict
0xd0135ac9…730f
0x34b655…2a6f
4 touches
1 conflict
0xd1b40f29…9b9d
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
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 0x427c9fc46b…895cee
Audit this contract →
← previous block·next block →recent activity