← previous blocknext block →recent activity
Analyzing
Block #106,380,627
25 transactions · 25 stateful · 2026-09-20 05:32:41 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,380,627 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w110w213w315w416w517w618w719w820w923w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74f1de76…50bf
0x34b655…2a6f
14 touches
21 conflicts
0xd2facdba…7a7e
0x34b655…2a6f
12 touches
15 conflicts
0x4984f7be…d515
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x92b49f44…ee4f
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
21 conflicts on slot 0x74f1de76a0…7f50bf
Audit this contract →
← previous block·next block →recent activity