← previous blocknext block →recent activity
Analyzing
Block #107,823,151
24 transactions · 21 stateful · 2026-09-25 06:36:44 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,823,151 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w513w215w016w117w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
14 touches
21 conflicts
0xa92c5c48…c3e2
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0xba9f9225…2ead
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x35801c67…bcc5
0x1b6862…e19c
12 touches
15 conflicts
0x66b74d22…ae69
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001f
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
21 conflicts on slot 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity