← previous blocknext block →recent activity
Analyzing
Block #106,790,856
20 transactions · 16 stateful · 2026-09-21 15:58:21 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,790,856 · 20 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
1w02w16w07w09w110w212w213w317w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f3c1376…49c7
0x34b655…2a6f
10 touches
10 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
10 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8a02d049…f481
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1b25f260…c429
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 0x5f3c13768e…e449c7
Audit this contract →
← previous block·next block →recent activity