← previous blocknext block →recent activity
Analyzing
Block #104,203,744
19 transactions · 19 stateful · 2026-09-12 14:30:30 UTC
Parallelism
84/100
Blocked
11%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,203,744 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0fd6c76…ddaf
0x34b655…2a6f
6 touches
3 conflicts
0x5c1fb664…cf50
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xce2f0b6e…0e05
0x34b655…2a6f
4 touches
1 conflict
0x168f7615…a8de
0x34b655…2a6f
4 touches
1 conflict
0x168f7615…a8dd
0x34b655…2a6f
4 touches
1 conflict
0x7af07457…58ce
0x34b655…2a6f
3 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 0xd0fd6c76d7…74ddaf
Audit this contract →
← previous block·next block →recent activity