← previous blocknext block →recent activity
Analyzing
Block #106,187,109
32 transactions · 27 stateful · 2026-09-19 13:18:42 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.47
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,187,109 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w19w010w111w214w218w320w421w222w523w624w725w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4ff9d99…1101
0x34b655…2a6f
18 touches
36 conflicts
0x0fc536fb…1aa1
0x34b655…2a6f
16 touches
28 conflicts
0x6b995497…5e06
0x34b655…2a6f
14 touches
21 conflicts
0x35b89cd8…5092
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa6464996…3af9
0x34b655…2a6f
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 0xd4ff9d99ee…c71101
Audit this contract →
← previous block·next block →recent activity