← previous blocknext block →recent activity
Analyzing
Block #106,224,694
36 transactions · 33 stateful · 2026-09-19 16:27:55 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,224,694 · 36 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
1w02w13w04w15w16w27w311w416w217w518w319w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x91fad112…eb29
0x34b655…2a6f
8 touches
6 conflicts
0x6e2c9711…3b7f
0x34b655…2a6f
8 touches
6 conflicts
0x5c6ab626…997f
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
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
6 conflicts on slot 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity