← previous blocknext block →recent activity
Analyzing
Block #92,273,633
17 transactions · 14 stateful · 2026-08-01 18:27:07 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,273,633 · 17 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
1w04w05w110w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5031114…58ac
0x34b655…2a6f
4 touches
1 conflict
0x03ea8e27…730f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe2fa00b0…457a
0x34b655…2a6f
4 touches
1 conflict
0x68a2902c…b23f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x3b56f79b…310f
0x34b655…2a6f
2 touches
0 conflicts
0x4e8c4408…d37a
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 0xc503111436…e358ac
Audit this contract →
← previous block·next block →recent activity