← previous blocknext block →recent activity
Analyzing
Block #91,027,070
13 transactions · 10 stateful · 2026-07-28 09:54:03 UTC
Parallelism
62/100
Blocked
40%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,027,070 · 13 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
2w03w14w25w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf2b36ab5…39d8
0x34b655…2a6f
6 touches
3 conflicts
0x442e26a3…e968
0x34b655…2a6f
6 touches
3 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
4 touches
1 conflict
0x53f16669…fcff
0x34b655…2a6f
4 touches
1 conflict
0x7013f73a…4daf
0x34b655…2a6f
4 touches
1 conflict
0x03fe94de…ffc8
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity