← previous blocknext block →recent activity
Analyzing
Block #105,643,549
16 transactions · 16 stateful · 2026-09-17 15:40:34 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,643,549 · 16 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
1w02w05w19w211w313w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75859aea…2e48
0x34b655…2a6f
10 touches
10 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0xe3684e08…c96a
0x34b655…2a6f
6 touches
3 conflicts
0xeddebb1d…4dd4
0x34b655…2a6f
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x3f47b9cc…2bb0
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
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
10 conflicts on slot 0x75859aea3d…102e48
Audit this contract →
← previous block·next block →recent activity