← previous blocknext block →recent activity
Analyzing
Block #107,823,159
27 transactions · 25 stateful · 2026-09-25 06:36:47 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,823,159 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w115w016w117w218w319w420w521w622w726w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2883066…14a6
0x34b655…2a6f
16 touches
28 conflicts
0x66fc0764…05fd
0x34b655…2a6f
16 touches
28 conflicts
0xba9f9225…2ead
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x69017fce…85c2
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
28 conflicts on slot 0xc288306643…9414a6
Audit this contract →
← previous block·next block →recent activity