← previous blocknext block →recent activity
Analyzing
Block #106,216,559
23 transactions · 23 stateful · 2026-09-19 15:46:58 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,216,559 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w110w112w215w316w317w418w519w620w722w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x535edd46…4d71
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x067b340d…5ce1
0x34b655…2a6f
8 touches
6 conflicts
0xe6040987…df02
0x34b655…2a6f
6 touches
3 conflicts
0x163c8eca…7b49
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x89bcc1d2…0ea0
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 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity