← previous blocknext block →recent activity
Analyzing
Block #108,797,001
22 transactions · 20 stateful · 2026-09-28 16:19:10 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,797,001 · 22 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
2w03w14w25w38w09w112w415w419w020w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724ba0cf…01c7
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc2249cf2…fa62
0x34b655…2a6f
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0x874b3e3d…09b8
0x34b655…2a6f
8 touches
6 conflicts
0x88fc2a68…3918
0x34b655…2a6f
8 touches
6 conflicts
0x955dc771…63a0
0x34b655…2a6f
8 touches
6 conflicts
0xada087b9…4aca
0x34b655…2a6f
8 touches
6 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 0x724ba0cf22…b301c7
Audit this contract →
← previous block·next block →recent activity