← previous blocknext block →recent activity
Analyzing
Block #91,103,737
38 transactions · 33 stateful · 2026-07-28 16:19:50 UTC
Parallelism
76/100
Blocked
61%
Avg conflicts / tx
1.29
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,103,737 · 38 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w06w17w08w112w213w314w416w017w118w219w121w323w125w126w528w229w332w633w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x28c714d9…9438
0xa6afd3…d132
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
8 touches
6 conflicts
0xe57ae7ed…f6da
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