← previous blocknext block →recent activity
Analyzing
Block #108,948,908
24 transactions · 23 stateful · 2026-09-29 05:07:01 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,948,908 · 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
1w02w13w29w210w312w413w114w215w316w417w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x3a3c1ed9…9dd5
0x34b655…2a6f
10 touches
10 conflicts
0x48719cbe…5484
0x34b655…2a6f
10 touches
10 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
10 touches
10 conflicts
0x342fe47d…42ae
0x34b655…2a6f
10 touches
10 conflicts
0xe3e67fe3…e754
0x37db7f…ec7b
10 touches
10 conflicts
0x1674d3d4…275f
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
15 conflicts on slot 0x676f9f01ee…dea8ac
Audit this contract →
← previous block·next block →recent activity