← previous blocknext block →recent activity
Analyzing
Block #106,542,402
19 transactions · 18 stateful · 2026-09-20 19:06:55 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,542,402 · 19 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
1w02w13w04w15w26w09w010w111w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71943d07…69fe
0x34b655…2a6f
10 touches
10 conflicts
0x906eae3c…27fa
0x34b655…2a6f
6 touches
3 conflicts
0xad862891…5d02
0x34b655…2a6f
6 touches
3 conflicts
0xb2560305…f27d
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xdbf974a4…b232
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0de7749d…5bef
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 0x71943d0702…9069fe
Audit this contract →
← previous block·next block →recent activity