← previous blocknext block →recent activity
Analyzing
Block #92,312,184
16 transactions · 16 stateful · 2026-08-01 21:41:01 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,312,184 · 16 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
2w03w19w212w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21605a79…d719
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x87ee379a…cd9e
0x34b655…2a6f
6 touches
3 conflicts
0xda46a376…f6a6
0x34b655…2a6f
4 touches
1 conflict
0x211d520a…bf67
0x34b655…2a6f
4 touches
1 conflict
0x4ec8d1b4…4e6e
0x34b655…2a6f
4 touches
1 conflict
0x58b8eda5…f15f
0x34b655…2a6f
4 touches
1 conflict
0x5e78c401…7a7e
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
3 conflicts on slot 0x21605a794b…a2d719
Audit this contract →
← previous block·next block →recent activity