← previous blocknext block →recent activity
Analyzing
Block #91,188,912
13 transactions · 12 stateful · 2026-07-28 23:28:18 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,188,912 · 13 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
1w02w13w04w05w17w28w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99d2cfb…dcdb
0x34b655…2a6f
8 touches
6 conflicts
0x7ee74e97…55f1
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x8fa97406…a574
0x34b655…2a6f
6 touches
3 conflicts
0x507215e0…cddd
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x866967b3…13fe
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 0xf99d2cfbd5…94dcdb
Audit this contract →
← previous block·next block →recent activity