← previous blocknext block →recent activity
Analyzing
Block #106,206,804
30 transactions · 28 stateful · 2026-09-19 14:57:52 UTC
Parallelism
63/100
Blocked
61%
Avg conflicts / tx
1.8
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,206,804 · 30 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
2w04w05w16w07w18w211w212w316w117w118w219w420w521w622w723w824w925w1028w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x703a441b…a516
0x34b655…2a6f
18 touches
36 conflicts
0x4118bd12…924a
0x34b655…2a6f
12 touches
15 conflicts
0x98568c43…ff4e
0x34b655…2a6f
12 touches
15 conflicts
0x315e07b8…9823
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0xe1e776cf…e39c
0x34b655…2a6f
8 touches
6 conflicts
0x6119ad89…63fe
0x34b655…2a6f
6 touches
3 conflicts
0x8ed9e490…9c51
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 0x703a441b69…0ba516
Audit this contract →
← previous block·next block →recent activity