← previous blocknext block →recent activity
Analyzing
Block #103,987,519
15 transactions · 13 stateful · 2026-09-11 20:10:59 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,987,519 · 15 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
1w04w17w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0xe188ad90…d23f
0x34b655…2a6f
6 touches
3 conflicts
0xa445b89a…c306
0x34b655…2a6f
6 touches
3 conflicts
0xda0a211b…0b24
0x34b655…2a6f
6 touches
3 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
4 touches
1 conflict
0xaaae2ec0…60a6
0x34b655…2a6f
4 touches
1 conflict
0xc11f059c…1eb9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
6 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity