← previous blocknext block →recent activity
Analyzing
Block #105,848,493
29 transactions · 24 stateful · 2026-09-18 08:53:29 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,848,493 · 29 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
1w02w05w07w19w110w016w020w121w223w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e68bd1f…e2a8
0x34b655…2a6f
8 touches
6 conflicts
0x8db32935…81a7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x7e28e55c…d05c
0x754704…b603
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x46a9fdea…9302
0x065c9d…c394
4 touches
1 conflict
0xc10b903d…2f54
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 0x8e68bd1fa1…fce2a8
Audit this contract →
← previous block·next block →recent activity