← previous blocknext block →recent activity
Analyzing
Block #106,199,329
39 transactions · 38 stateful · 2026-09-19 14:20:12 UTC
Parallelism
59/100
Blocked
66%
Avg conflicts / tx
2.08
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,199,329 · 39 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w08w29w010w111w214w215w316w419w621w322w323w424w727w228w430w931w1033w1236w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba73be23…c570
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x5717771c…45ed
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 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 0xba73be23ce…3fc570
Audit this contract →
← previous block·next block →recent activity