← previous blocknext block →recent activity
Analyzing
Block #105,636,211
20 transactions · 20 stateful · 2026-09-17 15:03:38 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,636,211 · 20 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
1w02w13w013w114w216w217w318w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5c35f87…2013
0x34b655…2a6f
8 touches
6 conflicts
0x941bd594…21fd
0x34b655…2a6f
6 touches
3 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x178a61ad…4958
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xb73a5ffd…ddee
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 0xc5c35f87f0…652013
Audit this contract →
← previous block·next block →recent activity