← previous blocknext block →recent activity
Analyzing
Block #91,404,229
17 transactions · 15 stateful · 2026-07-29 17:32:38 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,404,229 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w48w19w513w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x59fdf7d5…3c7c
0x34b655…2a6f
6 touches
3 conflicts
0xa73fa706…fe10
0x34b655…2a6f
4 touches
1 conflict
0xa751a2af…0ac0
0x34b655…2a6f
4 touches
1 conflict
0xab41643c…f9bf
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
10 conflicts on slot 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity