← previous blocknext block →recent activity
Analyzing
Block #106,215,697
37 transactions · 34 stateful · 2026-09-19 15:42:38 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.59
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,215,697 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w08w110w211w314w315w419w520w621w722w823w124w225w927w333w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf64b1101…663e
0x34b655…2a6f
14 touches
21 conflicts
0x2e90dcf9…1289
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
8 touches
6 conflicts
0xecf22f58…5939
0x34b655…2a6f
8 touches
6 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
21 conflicts on slot 0xf64b110162…6b663e
Audit this contract →
← previous block·next block →recent activity