← previous blocknext block →recent activity
Analyzing
Block #92,531,371
8 transactions · 8 stateful · 2026-08-02 16:03:21 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,531,371 · 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
4w05w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4c9a0df…dcd5
0x34b655…2a6f
4 touches
1 conflict
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0xff28ee17…414e
0x34b655…2a6f
4 touches
1 conflict
0x039f1f6c…3155
0x34b655…2a6f
4 touches
1 conflict
0x1fd19887…8e0e
0x34b655…2a6f
4 touches
1 conflict
0x29c1a140…099f
0x34b655…2a6f
4 touches
1 conflict
0x2cf53cbd…71da
0x34b655…2a6f
4 touches
1 conflict
0xf607560e…828a
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
1 conflict on slot 0xf4c9a0dfc5…fcdcd5
Audit this contract →
← previous block·next block →recent activity