← previous blocknext block →recent activity
Analyzing
Block #106,381,944
30 transactions · 27 stateful · 2026-09-20 05:39:18 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,381,944 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w013w014w116w121w222w223w324w425w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaad7031…6cd7
0x34b655…2a6f
12 touches
15 conflicts
0xba33378a…f1df
0x34b655…2a6f
12 touches
15 conflicts
0x20d149a4…d31c
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x3293a887…43ff
0x1b6862…e19c
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
15 conflicts on slot 0xfaad703149…806cd7
Audit this contract →
← previous block·next block →recent activity