← previous blocknext block →recent activity
Analyzing
Block #108,433,194
43 transactions · 39 stateful · 2026-09-27 09:47:00 UTC
Parallelism
58/100
Blocked
72%
Avg conflicts / tx
4.3
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #108,433,194 · 43 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w211w312w413w514w615w716w817w918w1019w1120w1222w1323w1433w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
30 touches
105 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
28 touches
91 conflicts
0x75e4cee9…0731
0x34b655…2a6f
26 touches
78 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
24 touches
66 conflicts
0x5969523e…5191
0x34b655…2a6f
24 touches
66 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
24 touches
66 conflicts
0x7006165a…df17
0x34b655…2a6f
24 touches
66 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
24 touches
66 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
105 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity