← previous blocknext block →recent activity
Analyzing
Block #106,216,714
20 transactions · 20 stateful · 2026-09-19 15:47:45 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,216,714 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w27w39w311w412w513w414w516w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5f77696…34c6
0x34b655…2a6f
10 touches
10 conflicts
0xe6040987…df02
0x34b655…2a6f
10 touches
10 conflicts
0xb550abea…2729
0x34b655…2a6f
6 touches
3 conflicts
0x6e2c9711…3b7f
0x34b655…2a6f
6 touches
3 conflicts
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0x29ec6563…bc8d
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0xe5f7769695…3834c6
Audit this contract →
← previous block·next block →recent activity