← previous blocknext block →recent activity
Analyzing
Block #105,848,651
21 transactions · 19 stateful · 2026-09-18 08:54:17 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,848,651 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w311w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe264d91f…d0e7
0x34b655…2a6f
14 touches
21 conflicts
0x29cd05f5…390c
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
6 touches
3 conflicts
0x7c8cf338…6e72
0x34b655…2a6f
4 touches
1 conflict
0x97394169…cfc0
0x34b655…2a6f
4 touches
1 conflict
0x9daafdf9…bb53
0x34b655…2a6f
4 touches
1 conflict
0xa57a72ed…64c2
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
21 conflicts on slot 0xe264d91f62…34d0e7
Audit this contract →
← previous block·next block →recent activity