← previous blocknext block →recent activity
Analyzing
Block #106,301,200
58 transactions · 43 stateful · 2026-09-19 22:52:58 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
1.59
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,301,200 · 58 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w08w211w114w217w318w019w421w134w548w450w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94dabb65…43a3
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x65903ef9…2567
0x34b655…2a6f
10 touches
10 conflicts
0x75f928fc…0465
0x34b655…2a6f
10 touches
10 conflicts
0x85a88798…f85e
0x34b655…2a6f
10 touches
10 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
10 touches
10 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 0x94dabb6529…f943a3
Audit this contract →
← previous block·next block →recent activity