← previous blocknext block →recent activity
Analyzing
Block #92,177,223
8 transactions · 8 stateful · 2026-08-01 10:22:16 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,177,223 · 8 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
1w03w14w26w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb0221be…c2b3
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x8e8d48a4…7a75
0x34b655…2a6f
2 touches
0 conflicts
0xba9f88e8…9c33
0x34b655…2a6f
2 touches
0 conflicts
0xbb461ef2…c57b
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 0xcb0221bebc…d1c2b3
Audit this contract →
← previous block·next block →recent activity