← previous blocknext block →recent activity
Analyzing
Block #92,067,982
10 transactions · 10 stateful · 2026-08-01 01:12:51 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,067,982 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a89094e…f5b2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2701beec…e869
0x34b655…2a6f
4 touches
1 conflict
0x0d816e2e…67a1
0x34b655…2a6f
2 touches
0 conflicts
0x2a53b0a1…a22d
0x34b655…2a6f
2 touches
0 conflicts
0x31734e80…921f
0x34b655…2a6f
2 touches
0 conflicts
0x3cf60d4f…b30b
0x34b655…2a6f
2 touches
0 conflicts
0x48a0f121…953b
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 0x9a89094e2b…f6f5b2
Audit this contract →
← previous block·next block →recent activity