← previous blocknext block →recent activity
Analyzing
Block #109,142,702
17 transactions · 17 stateful · 2026-09-29 21:25:15 UTC
Parallelism
30/100
Blocked
71%
Avg conflicts / tx
3.29
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #109,142,702 · 17 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w59w610w711w812w915w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x5565353a…6c9e
0x34b655…2a6f
16 touches
28 conflicts
0x5969523e…5191
0x34b655…2a6f
16 touches
28 conflicts
0x654dbfd0…02c9
0x34b655…2a6f
16 touches
28 conflicts
0x7499cc33…a306
0x34b655…2a6f
16 touches
28 conflicts
0x764dd399…b9fd
0x34b655…2a6f
16 touches
28 conflicts
0x98dd86bb…1edb
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
36 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity