← previous blocknext block →recent activity
Analyzing
Block #105,672,758
16 transactions · 16 stateful · 2026-09-17 18:07:37 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,672,758 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w19w010w111w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f5f775…010b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x51f30aee…bfbf
0x34b655…2a6f
4 touches
1 conflict
0xdaf02dea…dbd8
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
3 conflicts on slot 0xb5f5f77567…50010b
Audit this contract →
← previous block·next block →recent activity