← previous blocknext block →recent activity
Analyzing
Block #91,279,397
12 transactions · 10 stateful · 2026-07-29 07:04:21 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,279,397 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x110a671c…e284
0x34b655…2a6f
2 touches
0 conflicts
0x1b5ac71b…2ca7
0x34b655…2a6f
2 touches
0 conflicts
0x1d0dbea0…0ec9
0x34b655…2a6f
2 touches
0 conflicts
0x24103b39…4c2d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x6e6a81554a…499636
Audit this contract →
← previous block·next block →recent activity