← previous blocknext block →recent activity
Analyzing
Block #107,824,011
72 transactions · 55 stateful · 2026-09-25 06:41:04 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
2.86
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #107,824,011 · 72 txs across 20 waves · depth 20
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
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w17w28w39w410w512w122w623w744w245w649w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xea02471d…1542
0x34b655…2a6f
22 touches
55 conflicts
0x839c0c71…bada
0x34b655…2a6f
20 touches
45 conflicts
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0x6a9e408e…3721
0x34b655…2a6f
18 touches
36 conflicts
0x95523e2a…4c01
0x065c9d…c394
16 touches
28 conflicts
0x7b6d2deb…dde0
0x34b655…2a6f
14 touches
21 conflicts
0xae65f1ba…2f37
0x34b655…2a6f
14 touches
21 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity