← previous blocknext block →recent activity
Analyzing
Block #92,222,245
18 transactions · 16 stateful · 2026-08-01 14:08:39 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,222,245 · 18 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
2w03w14w07w210w211w313w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x083ff337…401b
0x34b655…2a6f
6 touches
3 conflicts
0x28e69eea…ff48
0x34b655…2a6f
6 touches
3 conflicts
0x1bd69a6a…2b8a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
6 touches
3 conflicts
0x4d947c59…8247
0x34b655…2a6f
4 touches
1 conflict
0x534ef679…ae9d
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 0x083ff337f4…99401b
Audit this contract →
← previous block·next block →recent activity