← previous blocknext block →recent activity
Analyzing
Block #104,870,776
20 transactions · 20 stateful · 2026-09-14 22:51:11 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,870,776 · 20 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
2w03w19w010w111w212w313w417w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc87e767e…4bba
0x34b655…2a6f
10 touches
10 conflicts
0xd7443f37…eb79
0x34b655…2a6f
10 touches
10 conflicts
0x0936440b…badb
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x81d72b15…8f95
0x34b655…2a6f
8 touches
6 conflicts
0xdd47784a…0783
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xa35509fa…5cb3
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
10 conflicts on slot 0xc87e767e77…974bba
Audit this contract →
← previous block·next block →recent activity