← previous blocknext block →recent activity
Analyzing
Block #106,953,094
41 transactions · 39 stateful · 2026-09-22 05:34:59 UTC
Parallelism
83/100
Blocked
51%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,953,094 · 41 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
1w03w14w05w16w07w18w29w310w414w217w320w321w426w228w434w639w440w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36dbc382…bd1f
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x8a3fecf6…b414
0xc8689a…ee79
6 touches
3 conflicts
0x229d2b7e…abdf
0x34b655…2a6f
6 touches
3 conflicts
0x23c8c8dd…7a42
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x36dbc382fa…0abd1f
Audit this contract →
← previous block·next block →recent activity