← previous blocknext block →recent activity
Analyzing
Block #91,135,755
19 transactions · 16 stateful · 2026-07-28 19:00:54 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,135,755 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w06w19w211w312w413w515w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58cec012…dcb8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x76faab64…5da0
0x34b655…2a6f
4 touches
1 conflict
0x8b3c9c3d…1acd
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 0x58cec0121e…01dcb8
Audit this contract →
← previous block·next block →recent activity