← previous blocknext block →recent activity
Analyzing
Block #106,394,560
27 transactions · 20 stateful · 2026-09-20 06:42:48 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,394,560 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w07w08w19w010w211w313w417w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee4fe1f7…3ead
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x24bb3547…c78e
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
4 touches
1 conflict
0x3b53436c…2ec3
0x34b655…2a6f
4 touches
1 conflict
0x474d0d1d…14af
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
6 conflicts on slot 0xee4fe1f73e…483ead
Audit this contract →
← previous block·next block →recent activity