← previous blocknext block →recent activity
Analyzing
Block #106,551,014
22 transactions · 21 stateful · 2026-09-20 19:50:15 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,551,014 · 22 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
1w03w05w06w110w111w113w114w215w017w318w420w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22ab637…7a8e
0x34b655…2a6f
8 touches
6 conflicts
0x7e18808e…c887
0x34b655…2a6f
8 touches
6 conflicts
0x559b9b44…9024
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
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 0xe22ab637d9…007a8e
Audit this contract →
← previous block·next block →recent activity