← previous blocknext block →recent activity
Analyzing
Block #91,276,639
15 transactions · 14 stateful · 2026-07-29 06:50:26 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,276,639 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5be6bae7…7e96
0x34b655…2a6f
6 touches
3 conflicts
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x2fd12b6c…02cc
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f3a6b4a…3819
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
3 conflicts on slot 0x5be6bae7c6…637e96
Audit this contract →
← previous block·next block →recent activity