← previous blocknext block →recent activity
Analyzing
Block #106,790,164
37 transactions · 33 stateful · 2026-09-21 15:54:52 UTC
Parallelism
51/100
Blocked
70%
Avg conflicts / tx
2.49
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,790,164 · 37 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w38w49w510w611w712w816w717w818w232w1335w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x4abfb389…18f4
0x34b655…2a6f
12 touches
15 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x527025ec…3d81
0x34b655…2a6f
12 touches
15 conflicts
0x6f5d7ccd…83d4
0x34b655…2a6f
12 touches
15 conflicts
0x7f0725e9…66f7
0x34b655…2a6f
10 touches
10 conflicts
0xd9c1bb1a…45de
0x34b655…2a6f
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