← previous blocknext block →recent activity
Analyzing
Block #91,543,740
34 transactions · 33 stateful · 2026-07-30 05:15:42 UTC
Parallelism
56/100
Blocked
73%
Avg conflicts / tx
2.79
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #91,543,740 · 34 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w08w19w010w111w212w313w415w116w417w518w620w221w523w725w826w929w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
10 touches
10 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
10 touches
10 conflicts
0xa8cff7bf…d80f
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity