← previous blocknext block →recent activity
Analyzing
Block #106,386,190
17 transactions · 17 stateful · 2026-09-20 06:00:41 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,386,190 · 17 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
1w05w16w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
16 touches
28 conflicts
0x1c549b52…80c6
0x34b655…2a6f
12 touches
15 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0x3ca268be…8865
0x34b655…2a6f
6 touches
3 conflicts
0x35c96674…ccb7
0x34b655…2a6f
4 touches
1 conflict
0xedc271c3…a7cc
0x34b655…2a6f
4 touches
1 conflict
0x08137337…8610
0x34b655…2a6f
4 touches
1 conflict
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 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity