← previous blocknext block →recent activity
Analyzing
Block #106,945,276
21 transactions · 21 stateful · 2026-09-22 04:55:37 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,945,276 · 21 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
1w02w13w04w15w29w010w111w215w216w318w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x858e40c0…7e30
0x34b655…2a6f
8 touches
6 conflicts
0xce307d4a…b8d8
0x34b655…2a6f
8 touches
6 conflicts
0xc22525cd…7db7
0x34b655…2a6f
8 touches
6 conflicts
0xc5d75bd2…1afb
0x34b655…2a6f
8 touches
6 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0x51aa664e…d3b8
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x5ad5e6de…e7ad
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
6 conflicts on slot 0x858e40c022…9e7e30
Audit this contract →
← previous block·next block →recent activity