← previous blocknext block →recent activity
Analyzing
Block #91,292,768
14 transactions · 14 stateful · 2026-07-29 08:11:38 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,292,768 · 14 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
2w03w14w27w38w49w510w511w613w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfed09e59…a493
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xb944ef48…7cb7
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc1da8f73…484c
0x34b655…2a6f
6 touches
3 conflicts
0x5d7e0e69…e6d2
0x34b655…2a6f
6 touches
3 conflicts
0x45d87399…4382
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xfed09e59c7…d6a493
Audit this contract →
← previous block·next block →recent activity