← previous blocknext block →recent activity
Analyzing
Block #91,982,172
12 transactions · 11 stateful · 2026-07-31 18:01:15 UTC
Parallelism
58/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,982,172 · 12 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
2w03w14w26w17w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd35783e3…c38a
0x34b655…2a6f
8 touches
6 conflicts
0x6b267bdf…b173
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xda27c764…7fab
0x34b655…2a6f
6 touches
3 conflicts
0x81e1b637…2b3b
0x34b655…2a6f
4 touches
1 conflict
0x81e1b637…2b3c
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xd35783e3af…b6c38a
Audit this contract →
← previous block·next block →recent activity