← previous blocknext block →recent activity
Analyzing
Block #106,186,067
23 transactions · 22 stateful · 2026-09-19 13:13:28 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,186,067 · 23 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
1w02w13w04w15w06w17w111w112w215w316w417w518w622w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36eb9d19…32f7
0x34b655…2a6f
10 touches
10 conflicts
0x05e1eba1…6491
0x34b655…2a6f
10 touches
10 conflicts
0x38a99e84…5df5
0x34b655…2a6f
10 touches
10 conflicts
0xd41f5136…97c6
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0x755c7b95…9404
0x34b655…2a6f
6 touches
3 conflicts
0x24574ba3…6505
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
10 conflicts on slot 0x36eb9d1999…be32f7
Audit this contract →
← previous block·next block →recent activity