← previous blocknext block →recent activity
Analyzing
Block #105,929,635
25 transactions · 21 stateful · 2026-09-18 15:42:45 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,929,635 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w17w29w311w412w522w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
12 touches
15 conflicts
0xe0e514b5…590b
0x34b655…2a6f
12 touches
15 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
8 touches
6 conflicts
0x7011529e…456e
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity