← previous blocknext block →recent activity
Analyzing
Block #106,555,712
14 transactions · 14 stateful · 2026-09-20 20:13:53 UTC
Parallelism
43/100
Blocked
50%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,555,712 · 14 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
1w02w13w24w35w46w57w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
16 touches
28 conflicts
0xf4497fd3…6ff0
0x34b655…2a6f
16 touches
28 conflicts
0xb8a4b8a7…e631
0x34b655…2a6f
16 touches
28 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0x7aa463de…e7b8
0x34b655…2a6f
14 touches
21 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xce307d4a…b8d8
0x34b655…2a6f
14 touches
21 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 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity