← previous blocknext block →recent activity
Analyzing
Block #106,945,277
17 transactions · 17 stateful · 2026-09-22 04:55:38 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,945,277 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w410w011w113w214w516w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0x4bb4d9a2…62bc
0x34b655…2a6f
10 touches
10 conflicts
0x51aa664e…d3b8
0x34b655…2a6f
10 touches
10 conflicts
0x5969523e…5191
0x34b655…2a6f
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
10 touches
10 conflicts
0x8f4e041c…01ae
0x34b655…2a6f
10 touches
10 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity