← previous blocknext block →recent activity
Analyzing
Block #106,215,798
23 transactions · 20 stateful · 2026-09-19 15:43:08 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,215,798 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w110w212w313w418w419w521w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe56a9d63…9fdf
0x34b655…2a6f
10 touches
10 conflicts
0x4fa87b90…ac9a
0x34b655…2a6f
8 touches
6 conflicts
0x581b829b…9578
0x34b655…2a6f
6 touches
3 conflicts
0xb7af7ea3…7d7d
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xe56a9d6305…219fdf
Audit this contract →
← previous block·next block →recent activity