← previous blocknext block →recent activity
Analyzing
Block #106,412,821
18 transactions · 15 stateful · 2026-09-20 08:14:42 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,412,821 · 18 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
1w02w03w14w26w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b662182…c900
0x34b655…2a6f
8 touches
6 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0x8d664414…3344
0x34b655…2a6f
4 touches
1 conflict
0xc20bb2f9…b221
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x176a8d88…fb6a
0x34b655…2a6f
4 touches
1 conflict
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 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
6 conflicts on slot 0x1b6621822a…e3c900
Audit this contract →
← previous block·next block →recent activity