← previous blocknext block →recent activity
Analyzing
Block #91,110,908
11 transactions · 11 stateful · 2026-07-28 16:55:55 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,110,908 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa538ac07…fc9f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xcda18b0b…6a4c
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x049f0b60…0440
0x34b655…2a6f
2 touches
0 conflicts
0x18b5d6f3…3d29
0x34b655…2a6f
2 touches
0 conflicts
0x1c0ef569…adf7
0x34b655…2a6f
2 touches
0 conflicts
0x231170f0…aa56
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 0xa538ac0729…5afc9f
Audit this contract →
← previous block·next block →recent activity