← previous blocknext block →recent activity
Analyzing
Block #106,566,345
27 transactions · 27 stateful · 2026-09-20 21:07:24 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,566,345 · 27 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
1w09w012w113w215w016w117w218w220w021w122w124w325w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xdf650d61…403c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0031
0x59df86…2780
6 touches
3 conflicts
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x08f9abf1…10bf
0x34b655…2a6f
4 touches
1 conflict
0x232b0b19…d946
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity