← previous blocknext block →recent activity
Analyzing
Block #106,367,009
29 transactions · 27 stateful · 2026-09-20 04:24:09 UTC
Parallelism
66/100
Blocked
52%
Avg conflicts / tx
1.79
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,367,009 · 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
1w02w14w25w09w011w012w013w314w115w118w219w320w421w522w623w724w825w128w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99ccc63c…6624
0x34b655…2a6f
14 touches
21 conflicts
0xf435f5d7…38fc
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8d664414…3344
0x34b655…2a6f
10 touches
10 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
10 touches
10 conflicts
0x3ca268be…8865
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0x54f7f60f…43cc
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
21 conflicts on slot 0x99ccc63cf7…146624
Audit this contract →
← previous block·next block →recent activity