← previous blocknext block →recent activity
Analyzing
Block #106,915,813
29 transactions · 28 stateful · 2026-09-22 02:27:20 UTC
Parallelism
66/100
Blocked
61%
Avg conflicts / tx
2.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,915,813 · 29 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
1w02w13w24w38w09w110w211w312w413w514w617w318w419w520w621w722w823w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9375a764…dca1
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x08e2f7cd…82ab
0x34b655…2a6f
14 touches
21 conflicts
0x3a49bf4a…7dee
0x34b655…2a6f
14 touches
21 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
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
36 conflicts on slot 0x9375a764b5…f0dca1
Audit this contract →
← previous block·next block →recent activity