← previous blocknext block →recent activity
Analyzing
Block #103,223,547
26 transactions · 24 stateful · 2026-09-09 03:56:44 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,223,547 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w18w211w012w114w015w116w218w120w121w222w323w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36aa792c…a68d
0x34b655…2a6f
6 touches
3 conflicts
0xcfb5d363…27f5
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0f763490…ff64
0x34b655…2a6f
4 touches
1 conflict
0x2905ed39…1865
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x541b0b94…a5ed
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 0x36aa792c6a…6da68d
Audit this contract →
← previous block·next block →recent activity