← previous blocknext block →recent activity
Analyzing
Block #106,216,729
29 transactions · 22 stateful · 2026-09-19 15:47:49 UTC
Parallelism
72/100
Blocked
55%
Avg conflicts / tx
1.34
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,216,729 · 29 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
2w03w04w15w06w113w114w216w217w319w420w122w527w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6040987…df02
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xcdff6645…d9ba
0x34b655…2a6f
6 touches
3 conflicts
0xd3b1d828…72e1
0x34b655…2a6f
6 touches
3 conflicts
0xf99856c4…370d
0x34b655…2a6f
6 touches
3 conflicts
0x498a8da3…3b0f
0x34b655…2a6f
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
15 conflicts on slot 0xe6040987fc…efdf02
Audit this contract →
← previous block·next block →recent activity