← previous blocknext block →recent activity
Analyzing
Block #104,198,878
20 transactions · 18 stateful · 2026-09-12 14:05:46 UTC
Parallelism
65/100
Blocked
33%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,198,878 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w011w113w214w316w417w518w019w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xc2eff740…b10d
0x34b655…2a6f
10 touches
10 conflicts
0xf72228f6…970c
0x34b655…2a6f
6 touches
3 conflicts
0xfc2493d3…6898
0x34b655…2a6f
4 touches
1 conflict
0x1408e7c7…f324
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
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
15 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity