← previous blocknext block →recent activity
Analyzing
Block #104,159,719
14 transactions · 13 stateful · 2026-09-12 10:47:05 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,159,719 · 14 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
6w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc2eff740…b10d
0x34b655…2a6f
6 touches
3 conflicts
0xfda69449…1d3b
0x34b655…2a6f
6 touches
3 conflicts
0x4ccfe55c…de03
0x34b655…2a6f
6 touches
3 conflicts
0x8299fe6c…5752
0x34b655…2a6f
4 touches
1 conflict
0x803eb45d…00bd
0x34b655…2a6f
4 touches
1 conflict
0x991e2e20…94a6
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity