← previous blocknext block →recent activity
Analyzing
Block #91,268,952
47 transactions · 45 stateful · 2026-07-29 06:11:15 UTC
Parallelism
62/100
Blocked
56%
Avg conflicts / tx
2.6
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #91,268,952 · 47 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w18w211w012w313w414w520w621w724w126w835w1436w937w1538w1639w1741w142w1543w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65c5c2dc…cdde
0x34b655…2a6f
18 touches
36 conflicts
0xf3d10975…0d07
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xea02471d…1542
0x34b655…2a6f
18 touches
36 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
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
36 conflicts on slot 0x65c5c2dca1…fccdde
Audit this contract →
← previous block·next block →recent activity