← previous blocknext block →recent activity
Analyzing
Block #106,452,938
17 transactions · 15 stateful · 2026-09-20 11:36:40 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,452,938 · 17 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
1w02w13w04w25w311w312w413w514w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb46c7ade…d4b0
0x34b655…2a6f
12 touches
15 conflicts
0x5fa29461…492c
0x34b655…2a6f
10 touches
10 conflicts
0x8d664414…3344
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
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 0xb46c7ade7f…44d4b0
Audit this contract →
← previous block·next block →recent activity