← previous blocknext block →recent activity
Analyzing
Block #91,135,729
16 transactions · 13 stateful · 2026-07-28 19:00:46 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,135,729 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2adc238a…b92b
0x34b655…2a6f
4 touches
1 conflict
0x305fcfb9…9005
0x34b655…2a6f
4 touches
1 conflict
0x600a406d…63f9
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
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 0x0f2d78b1bb…5e7363
Audit this contract →
← previous block·next block →recent activity