← previous blocknext block →recent activity
Analyzing
Block #106,156,173
17 transactions · 16 stateful · 2026-09-19 10:43:01 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,156,173 · 17 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
1w03w04w17w08w110w011w114w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x95fb9c30…63ad
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity