← previous blocknext block →recent activity
Analyzing
Block #91,410,946
22 transactions · 17 stateful · 2026-07-29 18:06:40 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,410,946 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w09w110w113w214w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x706169e5…8f5c
0x34b655…2a6f
4 touches
1 conflict
0x79af9fa6…7110
0x34b655…2a6f
4 touches
1 conflict
0x7bb8bdfc…f677
0x34b655…2a6f
4 touches
1 conflict
0x7bee8f0d…0855
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity