← previous blocknext block →recent activity
Analyzing
Block #107,651,424
54 transactions · 47 stateful · 2026-09-24 16:11:04 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
2.11
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #107,651,424 · 54 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w18w213w215w317w418w519w620w727w129w330w232w836w337w442w744w948w1351w452w553w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa6959190…72c1
0xd32edf…ff58
9 touches
10 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity