← previous blocknext block →recent activity
Analyzing
Block #108,641,401
34 transactions · 33 stateful · 2026-09-28 03:15:24 UTC
Parallelism
56/100
Blocked
64%
Avg conflicts / tx
1.97
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #108,641,401 · 34 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w28w09w110w211w312w413w514w615w716w817w923w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
8 touches
6 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
6 touches
3 conflicts
0x1a99f155…77b7
0x34b655…2a6f
6 touches
3 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
6 touches
3 conflicts
0x5f72d58f…c445
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity