← previous blocknext block →recent activity
Analyzing
Block #105,857,768
19 transactions · 15 stateful · 2026-09-18 09:40:10 UTC
Parallelism
74/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,857,768 · 19 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
2w03w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6677baa1…b6c5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfdc57502…d80e
0x34b655…2a6f
6 touches
3 conflicts
0x29f52043…0851
0x34b655…2a6f
4 touches
1 conflict
0x2d91ad27…b72a
0x34b655…2a6f
4 touches
1 conflict
0x36aa792c…a68d
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x4b84a880…6abb
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 0x6677baa1e2…0ab6c5
Audit this contract →
← previous block·next block →recent activity