← previous blocknext block →recent activity
Analyzing
Block #91,248,352
24 transactions · 22 stateful · 2026-07-29 04:27:21 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,248,352 · 24 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
1w02w16w07w18w29w311w412w513w616w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x529e53cf…38e4
0xa6afd3…d132
8 touches
6 conflicts
0x989252a1…d812
0xa6afd3…d132
8 touches
6 conflicts
0x6847107a…f468
0xa6afd3…d132
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
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: 0x48cba278…e2b48b
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity