← previous blocknext block →recent activity
Analyzing
Block #106,235,655
38 transactions · 35 stateful · 2026-09-19 17:23:08 UTC
Parallelism
60/100
Blocked
71%
Avg conflicts / tx
3.87
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,235,655 · 38 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w38w49w512w413w517w618w621w723w824w925w1026w1127w1228w1329w1434w835w936w1037w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9470055…bbf8
0x34b655…2a6f
26 touches
78 conflicts
0xe7aa7f4d…bf1c
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xfa046684…d50a
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
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
78 conflicts on slot 0xf94700553e…5dbbf8
Audit this contract →
← previous block·next block →recent activity