← previous blocknext block →recent activity
Analyzing
Block #106,215,512
33 transactions · 31 stateful · 2026-09-19 15:41:42 UTC
Parallelism
76/100
Blocked
61%
Avg conflicts / tx
1.91
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,215,512 · 33 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
1w02w13w28w19w210w011w112w213w317w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6e64efa…fbce
0x34b655…2a6f
16 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
14 touches
21 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
14 touches
21 conflicts
0x581b829b…9578
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x163c8eca…7b49
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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
28 conflicts on slot 0xe6e64efa4f…f7fbce
Audit this contract →
← previous block·next block →recent activity