← previous blocknext block →recent activity
Analyzing
Block #104,204,441
17 transactions · 15 stateful · 2026-09-12 14:34:03 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,204,441 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w08w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe769c6e8…a9f2
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x1d48c0e2…b62e
0x34b655…2a6f
6 touches
3 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
6 touches
3 conflicts
0x6c28863e…840e
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 0xe769c6e841…d8a9f2
Audit this contract →
← previous block·next block →recent activity