← previous blocknext block →recent activity
Analyzing
Block #106,053,187
19 transactions · 17 stateful · 2026-09-19 02:04:44 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,053,187 · 19 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
1w02w14w15w26w07w19w314w416w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e9b4cfc…4a39
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x0c892160…6d38
0x34b655…2a6f
6 touches
3 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x5e9b4cfc2e…294a39
Audit this contract →
← previous block·next block →recent activity