← previous blocknext block →recent activity
Analyzing
Block #105,643,986
20 transactions · 19 stateful · 2026-09-17 15:42:46 UTC
Parallelism
65/100
Blocked
68%
Avg conflicts / tx
1.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,643,986 · 20 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
1w02w13w26w37w08w19w210w311w112w313w414w517w419w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe468b15b…6f6d
0x34b655…2a6f
8 touches
6 conflicts
0x1cc32af8…dcc2
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x544745e8…d72e
0x34b655…2a6f
8 touches
6 conflicts
0x90a021f0…f922
0x34b655…2a6f
8 touches
6 conflicts
0x947bb79d…6458
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0xe468b15bd5…536f6d
Audit this contract →
← previous block·next block →recent activity