← previous blocknext block →recent activity
Analyzing
Block #106,017,657
14 transactions · 12 stateful · 2026-09-18 23:05:56 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,017,657 · 14 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
1w02w03w04w05w18w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fbd0a79…626a
0x34b655…2a6f
6 touches
3 conflicts
0xfe30b1dc…1ede
0xa6afd3…d132
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x6435bd34…b160
0x34b655…2a6f
4 touches
1 conflict
0x735a86cd…b64d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd91f9aca…3735
0x34b655…2a6f
4 touches
1 conflict
0xfd69dfe7…0bb7
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 0x4fbd0a7965…4c626a
Audit this contract →
← previous block·next block →recent activity