← previous blocknext block →recent activity
Analyzing
Block #106,954,306
20 transactions · 20 stateful · 2026-09-22 05:41:05 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,954,306 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w08w09w110w111w212w313w215w117w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cabc566…f385
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0xa4a1ecf7…9e63
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x9375a764…dca1
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
6 conflicts on slot 0x0cabc56642…c3f385
Audit this contract →
← previous block·next block →recent activity