← previous blocknext block →recent activity
Analyzing
Block #104,332,235
10 transactions · 10 stateful · 2026-09-13 01:22:19 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,332,235 · 10 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
1w03w16w27w38w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7ad1b86…f564
0x34b655…2a6f
6 touches
3 conflicts
0x46286411…51fc
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x5b0a33d1…f825
0x34b655…2a6f
4 touches
1 conflict
0x6bab0076…422b
0x34b655…2a6f
4 touches
1 conflict
0x6bf96f12…29ba
0x34b655…2a6f
4 touches
1 conflict
0x70e97fae…53f2
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
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 0xe7ad1b863a…85f564
Audit this contract →
← previous block·next block →recent activity