← previous blocknext block →recent activity
Analyzing
Block #107,824,471
25 transactions · 24 stateful · 2026-09-25 06:43:23 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.56
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,824,471 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w18w09w112w013w214w315w416w417w518w619w720w821w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd07321…1c31
0x34b655…2a6f
14 touches
21 conflicts
0x8c35871e…8931
0x34b655…2a6f
12 touches
15 conflicts
0x49fc0524…1bad
0x34b655…2a6f
10 touches
10 conflicts
0x0d62a56d…43b1
0x34b655…2a6f
10 touches
10 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x5060cdde…445d
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xdcd0732149…7d1c31
Audit this contract →
← previous block·next block →recent activity