← previous blocknext block →recent activity
Analyzing
Block #92,767,131
15 transactions · 14 stateful · 2026-08-03 11:50:18 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,767,131 · 15 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
2w03w14w25w36w27w38w39w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb4cb196…8c4a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9ff9e7bd…2490
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x8e84ca5a…1f3b
0x34b655…2a6f
5 touches
3 conflicts
0xbc87a0c8…a6e1
0x34b655…2a6f
4 touches
1 conflict
0xab41643c…f9bf
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
6 conflicts on slot 0xfb4cb196b2…e68c4a
Audit this contract →
← previous block·next block →recent activity