← previous blocknext block →recent activity
Analyzing
Block #92,067,800
9 transactions · 8 stateful · 2026-08-01 01:11:56 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,067,800 · 9 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a2f19ef…f94e
0x34b655…2a6f
4 touches
1 conflict
0xa4631748…0876
0x34b655…2a6f
4 touches
1 conflict
0xb02cde1d…3115
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x11431f9d…42c5
0x34b655…2a6f
3 touches
1 conflict
0x0ca3397e…3644
0x34b655…2a6f
2 touches
0 conflicts
0x0d120b7c…64ef
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 0x5a2f19effd…cef94e
Audit this contract →
← previous block·next block →recent activity