← previous blocknext block →recent activity
Analyzing
Block #106,453,209
44 transactions · 38 stateful · 2026-09-20 11:38:02 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
2.05
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,453,209 · 44 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
1w02w04w15w16w27w38w49w514w623w129w731w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
12 touches
15 conflicts
0x52e69143…95ad
0x065c9d…c394
12 touches
15 conflicts
0xce827910…ff22
0x065c9d…c394
12 touches
15 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x06e40499…165e
0x34ae4d…3fc5
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity