← previous blocknext block →recent activity
Analyzing
Block #106,016,920
26 transactions · 21 stateful · 2026-09-18 23:02:13 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,016,920 · 26 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
1w03w04w18w111w213w314w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x156f9d43…a708
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x26b0fa60…c1cc
0x34b655…2a6f
4 touches
1 conflict
0x2dc55ab4…4ff2
0x34b655…2a6f
4 touches
1 conflict
0x3f152ba8…cea6
0x34b655…2a6f
4 touches
1 conflict
0x45885570…ed97
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity