← previous blocknext block →recent activity
Analyzing
Block #91,191,183
27 transactions · 23 stateful · 2026-07-28 23:39:44 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,191,183 · 27 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
2w04w15w07w08w19w210w311w415w116w017w118w120w221w323w424w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xcc351d6d…256b
0x34b655…2a6f
8 touches
6 conflicts
0x1b7ae237…b0e9
0x34b655…2a6f
6 touches
3 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
6 touches
3 conflicts
0x72dfc699…6dc3
0x34b655…2a6f
6 touches
3 conflicts
0x97ea91d9…00b5
0x34b655…2a6f
6 touches
3 conflicts
0x8a7bbbe6…3ca4
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: 0x48cba278…e2b48b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity