← previous blocknext block →recent activity
Analyzing
Block #105,869,763
13 transactions · 13 stateful · 2026-09-18 10:40:32 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,869,763 · 13 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
4w06w19w011w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3836a730…b3a9
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x52641874…dd75
0x34b655…2a6f
3 touches
1 conflict
0x65e795ca…0320
0x34b655…2a6f
2 touches
0 conflicts
0x37df7523…ccbb
0x754704…b603
2 touches
0 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
1 conflict on slot 0x3836a73066…21b3a9
Audit this contract →
← previous block·next block →recent activity