← previous blocknext block →recent activity
Analyzing
Block #107,824,340
44 transactions · 39 stateful · 2026-09-25 06:42:44 UTC
Parallelism
61/100
Blocked
77%
Avg conflicts / tx
3.11
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #107,824,340 · 44 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
1w02w13w24w35w16w27w411w215w320w221w323w424w525w626w727w828w929w1040w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
26 touches
78 conflicts
0x49890ced…6f23
0x34b655…2a6f
20 touches
45 conflicts
0xba1edffb…323e
0x34b655…2a6f
14 touches
21 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0xa0998a89…1f5a
0x34b655…2a6f
14 touches
21 conflicts
0xb4f45d9b…503e
0x34b655…2a6f
12 touches
15 conflicts
0x9a8f4f50…8234
0x34b655…2a6f
12 touches
15 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
78 conflicts on slot 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity