← previous blocknext block →recent activity
Analyzing
Block #104,332,175
16 transactions · 13 stateful · 2026-09-13 01:22:01 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,332,175 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w09w113w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x5d6da397…6c5c
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x28b01e5f…ced5
0xb754ba…508d
4 touches
1 conflict
0x28b01e5f…ced6
0xb754ba…508d
4 touches
1 conflict
0x2d6af7d3…5e30
0x34b655…2a6f
3 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 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: USDC (USDC)
1 conflict on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity