← previous blocknext block →recent activity
Analyzing
Block #103,041,017
23 transactions · 21 stateful · 2026-09-08 12:36:33 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,041,017 · 23 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
1w02w13w07w18w29w010w113w214w315w316w421w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a1cdfbe…3b93
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x6a58ad35…d96b
0x34b655…2a6f
4 touches
1 conflict
0xa527a5f0…89ca
0x34b655…2a6f
4 touches
1 conflict
0xb9a0dde5…9e2b
0x34b655…2a6f
4 touches
1 conflict
0xc124a42a…7ffc
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 0x9a1cdfbe8d…053b93
Audit this contract →
← previous block·next block →recent activity