← previous blocknext block →recent activity
Analyzing
Block #106,387,903
21 transactions · 20 stateful · 2026-09-20 06:09:18 UTC
Parallelism
52/100
Blocked
55%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,387,903 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w39w411w512w613w714w815w917w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc851ab8…6a15
0x34b655…2a6f
18 touches
36 conflicts
0xc9a6e112…69cc
0x34b655…2a6f
16 touches
28 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
10 touches
10 conflicts
0x5d1ac445…5233
0x34b655…2a6f
10 touches
10 conflicts
0x8d175439…fb79
0x34b655…2a6f
6 touches
3 conflicts
0x4984f7be…d515
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
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
36 conflicts on slot 0xcc851ab856…876a15
Audit this contract →
← previous block·next block →recent activity