← previous blocknext block →recent activity
Analyzing
Block #106,100,141
14 transactions · 12 stateful · 2026-09-19 06:01:01 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,100,141 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w18w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b2
0x37db7f…ec7b
6 touches
3 conflicts
0x7f430e47…4cbd
0x37db7f…ec7b
6 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0xd51e5dd7…8bb6
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x90d24713…b88c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x73b87bc2…457a
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: 0x37db7fbf…3eec7b
3 conflicts on slot 0x8a35acfbc1…6bd1b2
Audit this contract →
← previous block·next block →recent activity