← previous blocknext block →recent activity
Analyzing
Block #108,444,197
41 transactions · 39 stateful · 2026-09-27 10:42:23 UTC
Parallelism
59/100
Blocked
77%
Avg conflicts / tx
3.05
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #108,444,197 · 41 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w28w39w210w311w412w513w614w715w816w917w1018w1122w129w231w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0x1fb6e47f…b99a
0x34b655…2a6f
16 touches
28 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
16 touches
28 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
16 touches
28 conflicts
0x5969523e…5191
0x34b655…2a6f
16 touches
28 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
16 touches
28 conflicts
0x7006165a…df17
0x34b655…2a6f
16 touches
28 conflicts
0x8f4e041c…01ae
0x34b655…2a6f
16 touches
28 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
66 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity